Hi Larry,
User #1 stayed on the same record in edit mode the whole time and did not ever move the record pointer. Whereas User #2 started on the same record as User #1, pressed Edit and got my message -Try later. Record in use.- So then User #2 SKIP-1 to the previous record, then SKIP back to the original record and pressed Edit again and did not get my message. Then User #2 went to first field in the form to edit the value and got the sys msg - Record already in use by another user.-
I added an ON ERROR trap to the Error Event of each field on my form. Now, my error msg is displayed instead of the system message and the user gets taken out of edit mode and does not get ejected from the application by Cancel or Ignore button choices, as in the sys msg.
I think I am starting to understand the problem, but I was trying to avoid going into every field on the form and putting the ON ERROR trap routine in each field. I was trying to isolate the ON ERROR trap to the Edit button and save a bunch of coding and time, but I don't think I have much choice.
Thanks for the help. You have rescued me again.
Steve Kramer
Kramer & Kramer Design
"Home of Go Cartoons"
Web Site:
www.stephenkramer.comWould you believe Far Side Lite?
More than 270 original cartoons.