Hallo.
I want to create an indexer form in a database which many users enter data into (one big table called index).
At present, I have a page field - each user indexes a page of 50 records at a time - to avoid any conflicts.
I was wondering, though, if there was a simpler way to protect data?
I had an idea for an in_use field that might go (roughly) a little like:
in_use=false
DoCmd.GoToRecord , , acNext
while in_use
DoCmd.GoToRecord , , acNext
wend
in_use=true
The trouble is, I'm still not convinced that this would be totally safe, and can't help feeling that there must be a simple setting built into Access 97 that already allows for this kind of protection.
Anyone?
All help very appreciated, as usual
Douglas JL If it don't make you laugh, it ain't true.
I want to create an indexer form in a database which many users enter data into (one big table called index).
At present, I have a page field - each user indexes a page of 50 records at a time - to avoid any conflicts.
I was wondering, though, if there was a simpler way to protect data?
I had an idea for an in_use field that might go (roughly) a little like:
in_use=false
DoCmd.GoToRecord , , acNext
while in_use
DoCmd.GoToRecord , , acNext
wend
in_use=true
The trouble is, I'm still not convinced that this would be totally safe, and can't help feeling that there must be a simple setting built into Access 97 that already allows for this kind of protection.
Anyone?
All help very appreciated, as usual
Douglas JL If it don't make you laugh, it ain't true.