In ACCESS97, you could make changes to the Forms, Reports, etc, while other users were logged on. They would then get the changes when they logged off and logged on again. We have converted to 2002, and now you can not make any changes unless you are the only user logged on. Is this a standard of 2002, or can this be "optioned' out? Thanks in advance for any help.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Modify a database when others are logged on.
- Thread starter NewTeki
- Start date
You should never be making changes to objects while users are in the smae copy of the database. If you have a nmulti-user database, you really, really, really should split it into a front end and a back end. There are tons of threads here about how to go about it. I've got a couple of pages on it in the Deploying Databases section (under Developers') of my website. It's critical.
You should have one copy of the front end sitting on your server, and when the user wants to get into the database he clicks on a shortcut to a batch file that checks if there is a current front end on the user's PC, and copies it over, if not. Then it will fire up the local copy of the front end, which will link to the tables in the back end.
With this method, you make changes to a development copy of the front end and when you're sure they're right, you put it on the server so a new version can be rolled out to the users.
I know it sounds like a lot of work, and it often takes people an afternoon to grok the whole thing, but it is a really crucial thing to do, if you care about not losing your database to corruption, not having your users get bogged down by sharing the same front end, and being able to make changes to your database in a safe way.
Jeremy
==
Jeremy Wallace
AlphaBet City Dataworks
Professional Development for Clients Large and Small
Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.
You should have one copy of the front end sitting on your server, and when the user wants to get into the database he clicks on a shortcut to a batch file that checks if there is a current front end on the user's PC, and copies it over, if not. Then it will fire up the local copy of the front end, which will link to the tables in the back end.
With this method, you make changes to a development copy of the front end and when you're sure they're right, you put it on the server so a new version can be rolled out to the users.
I know it sounds like a lot of work, and it often takes people an afternoon to grok the whole thing, but it is a really crucial thing to do, if you care about not losing your database to corruption, not having your users get bogged down by sharing the same front end, and being able to make changes to your database in a safe way.
Jeremy
==
Jeremy Wallace
AlphaBet City Dataworks
Professional Development for Clients Large and Small
Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.
- Status
Similar threads
- Locked
- Question
- Locked
- Question