D
dhstein
Until now, the database I'm developing has been one which only I update and
the users just read information. So I keep the main copy (unsplit) and
distribute a new version (splitting the database) when I do updates. This
allows me to easily backup the database and ensure that there are no data
corruption problems. Pretty soon, there will be a need for another person to
update one of the tables. So I have 2 choices.
1) Keep the split database on the network and do regular backups - probably
the recommended solution.
2) Provide a second database with the one table that gets updated and
periodically import the updated data into the original database.
I would like to use option 1. But I'm concerned about Access corrupting the
database as well as other issues like record locking for multiple users
updating at the same time. So what is the track record for Access and table
corruption. Is this a non-issue ? Can I back up an open database or does it
have to be closed (users might leave the application open when the backup is
running) What special handling do I need when I open a recordset if multiple
users will be updating? Please let me know what experiences you've had with
these types of issues. Thanks for any advice.
the users just read information. So I keep the main copy (unsplit) and
distribute a new version (splitting the database) when I do updates. This
allows me to easily backup the database and ensure that there are no data
corruption problems. Pretty soon, there will be a need for another person to
update one of the tables. So I have 2 choices.
1) Keep the split database on the network and do regular backups - probably
the recommended solution.
2) Provide a second database with the one table that gets updated and
periodically import the updated data into the original database.
I would like to use option 1. But I'm concerned about Access corrupting the
database as well as other issues like record locking for multiple users
updating at the same time. So what is the track record for Access and table
corruption. Is this a non-issue ? Can I back up an open database or does it
have to be closed (users might leave the application open when the backup is
running) What special handling do I need when I open a recordset if multiple
users will be updating? Please let me know what experiences you've had with
these types of issues. Thanks for any advice.