Neil Ginsberg wrote:
> Well, that took care of the issue with the "record has been changed" error
> message. And, though the other error was intermittent so I can't directly
> test it, I'm sure having the timestamp field will take care of that other
> one, as well. Thanks again for your help!

D'OH! that'll teach me to read the whole thread before replying :-)

--
This sig left intentionally blank