T
ThunderTek
I am writing a database for work. I have been good on getting very few
corruption error, however when I do get a corruption I cannot fix it with the
Compact and Repair Feature. It appears that the corruption is on the front
end.
The database is located on a server and multiple people are able to access
it at one time. I would like to install the front end on every PC, but I
have a problem. Everyone that accesses this front end is able to input data
into fields. These fields may be written into by more than one person at one
time. So, if a persone is logged into the same for and attempts to input
data into the same field; how does access handle this data coming from
seperate locations. For this reason I placed locking code into the front end
so that it only allows for one user to enter a data entry form at a time.
This is why the front end is server based, so that everyone loads the same
code and sees the same locking variables.
So the question is, how can I keep from getting the front end forms corrupted?
Hope this is enough info.
corruption error, however when I do get a corruption I cannot fix it with the
Compact and Repair Feature. It appears that the corruption is on the front
end.
The database is located on a server and multiple people are able to access
it at one time. I would like to install the front end on every PC, but I
have a problem. Everyone that accesses this front end is able to input data
into fields. These fields may be written into by more than one person at one
time. So, if a persone is logged into the same for and attempts to input
data into the same field; how does access handle this data coming from
seperate locations. For this reason I placed locking code into the front end
so that it only allows for one user to enter a data entry form at a time.
This is why the front end is server based, so that everyone loads the same
code and sees the same locking variables.
So the question is, how can I keep from getting the front end forms corrupted?
Hope this is enough info.