B
Bonnie
Hi there, thanks for looking. Using A02 on XP. Would
really appreciate a few folks commenting on which way I
should go with this challenge.
Have about 6 frontend DB's in our share drive (S:\RPS)
with my single backend DB in a protected area in the share
drive (S:\RPS\Security). 2-3 are so frequently used that
lots of folks tend to leave them open through the day to
flip back and forth as work demands.
My problem is that every few weeks or so one of the DB's
will give someone the message "Cannot save at this time,
record currently locked" (wordage not exact, just as I
recall). I've discovered this happens when someone edits
or creates a record and leaves it open in edit mode
(pencil on left bar), gets on the phone or something else,
la de da, time goes by, someone else 'flips' back to the
DB that they may also have had sitting open and tries to
add a record, BAM, message "cannot save..."
My solution can go two ways as I see it:
I could put multiple copies of the files out in the S:\RPS
folder and name them DB1, DB2, etc. Then each user would
have their own DB.
OR; I could go the more labor intensive route and copy the
file to each user's C or G drive which is specific to each
PC.
Potential problem with my solutions: if a user has a 'new'
record open still in edit mode, will the error still occur
even if I do one of the two things listed above? If so, is
there a better way? Should I return to investigating
using a Timer Event Procedure to at least close any open
form that has a record showing whether in edit mode or not?
REALLY, REALLY need some expert advice on this.
P.S. I'm not a programmer but can use events and some code.
Thanks in advance for taking your time to read this and
hopefully, giving me some advice or comments. LUV U GUYS!
really appreciate a few folks commenting on which way I
should go with this challenge.
Have about 6 frontend DB's in our share drive (S:\RPS)
with my single backend DB in a protected area in the share
drive (S:\RPS\Security). 2-3 are so frequently used that
lots of folks tend to leave them open through the day to
flip back and forth as work demands.
My problem is that every few weeks or so one of the DB's
will give someone the message "Cannot save at this time,
record currently locked" (wordage not exact, just as I
recall). I've discovered this happens when someone edits
or creates a record and leaves it open in edit mode
(pencil on left bar), gets on the phone or something else,
la de da, time goes by, someone else 'flips' back to the
DB that they may also have had sitting open and tries to
add a record, BAM, message "cannot save..."
My solution can go two ways as I see it:
I could put multiple copies of the files out in the S:\RPS
folder and name them DB1, DB2, etc. Then each user would
have their own DB.
OR; I could go the more labor intensive route and copy the
file to each user's C or G drive which is specific to each
PC.
Potential problem with my solutions: if a user has a 'new'
record open still in edit mode, will the error still occur
even if I do one of the two things listed above? If so, is
there a better way? Should I return to investigating
using a Timer Event Procedure to at least close any open
form that has a record showing whether in edit mode or not?
REALLY, REALLY need some expert advice on this.
P.S. I'm not a programmer but can use events and some code.
Thanks in advance for taking your time to read this and
hopefully, giving me some advice or comments. LUV U GUYS!