Strikes me that you've got two things you need to fix.
Your application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables). Only the back-end should be on the server: each user should have
his/her own copy of the front-end, preferably on their hard drive.
You should never be making changes on a production database: your changes
should be made on a test database (the front-end). Once you know that the
change is successful, replace everyone's front-end. You can use the free
utility Tony Toews has at http://www.granite.ab.ca/access/autofe.htm
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Krzysztof" <u11875[ at ]uwe> wrote in message news:57bf35bebb6ac[ at ]uwe...
[Quoted Text] > Hello, Dzien dobry! (Good Morning) > > Having to update a db frequently can be frustrating when i have to wait > for > people to get out of it. So i have a secured db, can i do something so I > can > update whenever i want? i have heard of something, i think it can be > done, > any suggestions? > > TIA > ~K > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200511/1
|