View Single Post
  #10  
Old November 23rd, 2005, 04:48 PM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default When "Splitting" isn't enough

In addition to all of the other ideas...

One thing you could try is setting a global flag (in the first form)
indicating that you are starting a new entry. Then, on opening each
subsequent form, check this flag - if it is set, allow the user to make
edits; if it is not set, don't allow edits.

Carl Rapson

"Geogeek" wrote in message
...
I've split my test run and most everything works great. However, how do I
provide a multi-user environment that does not allow each user to
view/access
existing records (to prevent accidental data overwritting, etc.), but at
the
same time allow the user to "Go Back" to a previous page (form) to make
edits
while entering data?

I've performed all the trial-by-error methods that I can think of, in
addition to reading the "Access Bible", but I can't seem to get over this
last major hurdle. Please help before I hurdle myself over something very
high and steep!

Mucho thanks!!!