I need reference books! I have been crowned the "Access Guru" at my office only because I know more than any of them, which doesn't mean much.
We had a fairly simple database that 2 or 3 people were using at the same time. It houses client data regarding their equipment and support status. Within the last few months, we have had about 10 part-timers come to help with the administrative tasks of notifying clients when their support agreement will expire as well as basic data entry.
Because of the increased traffic, I chose to split the database into one backend with the data and 2 frontends, a main one and a data entry one. Now, the databases are corrupting. I back them up and compact and repair them every morning. I have been able to find some instances where user error caused the corruption and we have since correct that.
Yesterday, I realized that the employee who used the database in its infantry, when it was a simple, stand-alone database for 2 people, is still using it as such.
I know that when a database is in a multi-user state, you need to use it differently than if was a single database on your hard drive. I just don't know what those differences are.
I would greatly appreciate any suggestions on Access 2000 books that are geared toward LAN / Multi-User environments.
I can create any report they want or pull any data they need, but as for why they keep breaking the database, I am at a loss!
Thanks!!!!!!
We had a fairly simple database that 2 or 3 people were using at the same time. It houses client data regarding their equipment and support status. Within the last few months, we have had about 10 part-timers come to help with the administrative tasks of notifying clients when their support agreement will expire as well as basic data entry.
Because of the increased traffic, I chose to split the database into one backend with the data and 2 frontends, a main one and a data entry one. Now, the databases are corrupting. I back them up and compact and repair them every morning. I have been able to find some instances where user error caused the corruption and we have since correct that.
Yesterday, I realized that the employee who used the database in its infantry, when it was a simple, stand-alone database for 2 people, is still using it as such.
I know that when a database is in a multi-user state, you need to use it differently than if was a single database on your hard drive. I just don't know what those differences are.
I would greatly appreciate any suggestions on Access 2000 books that are geared toward LAN / Multi-User environments.
I can create any report they want or pull any data they need, but as for why they keep breaking the database, I am at a loss!
Thanks!!!!!!
