outofpractice
Registered User.
- Local time
- Today, 12:04
- Joined
- May 10, 2011
- Messages
- 32
I'm getting ready to push out a new DB for approximately 20 people to use - it is used to document names/addresses & then generate new files with updated addresses. A prior version of this had usage that generated approximately 40,000 records per year. At any given time there would be about 10 - 12 users in it at once.
My question is what is the best way to distribute this DB? Right now I plan to split the database, but I don't know if I should send the users a shortcut to use the main form, have them all use the same front-end, or create a copy of the front end for each user.
On my prior version everyone used a shortcut until more & more people were using it & it seemed to get very slow. Eventually I made everyone their own front-end to open and enter from because I had read that would increase performance, but it really did not seem to do much.
Thanks for any input into best practices!
My question is what is the best way to distribute this DB? Right now I plan to split the database, but I don't know if I should send the users a shortcut to use the main form, have them all use the same front-end, or create a copy of the front end for each user.
On my prior version everyone used a shortcut until more & more people were using it & it seemed to get very slow. Eventually I made everyone their own front-end to open and enter from because I had read that would increase performance, but it really did not seem to do much.
Thanks for any input into best practices!