Access_guy49
Registered User.
- Local time
- Today, 18:31
- Joined
- Sep 7, 2007
- Messages
- 462
Hey Everyone, I have created a Database on our network.
Now I know that people can open the database front end right on a network share without a problem. And call me crazy but i just prefer that the front end database be stored on a user's local machine. So i created a method that, on open, tests to see if there is a newer version of my front end on the server, then if there is, it copies it, and replaces the existing client front end.
This allows me to update the databse and know that all users who have a copy on their machine will get an updated version the next time they use the database..
Does anyone else bother with this? Does anyone have a good method for doing this that perhaps i have not considered?
Now I know that people can open the database front end right on a network share without a problem. And call me crazy but i just prefer that the front end database be stored on a user's local machine. So i created a method that, on open, tests to see if there is a newer version of my front end on the server, then if there is, it copies it, and replaces the existing client front end.
This allows me to update the databse and know that all users who have a copy on their machine will get an updated version the next time they use the database..
Does anyone else bother with this? Does anyone have a good method for doing this that perhaps i have not considered?