onestopfinancial
asked on
Multiuser network issues
Hello,
I have 2 users of my database, which is on my computer, the users access the database via a shared folder. Thorughout the day, while I'm designing forms/reports/queries etc. and other users try to enter data we get messages saying exclusive access is required and any changes might not save properly.
Obviously there is an issue of useability because we have to hollar at each other to close forms so someone can do something.
I have a feeling someone is going to say I need a separate front-end on the user machines so users aren't working directly in the database, however I am no where near fathoming creating a VB front-end, at this point.
How can I fix this issue without creating a front-end? Do I need a server? Any ideas?
I have 2 users of my database, which is on my computer, the users access the database via a shared folder. Thorughout the day, while I'm designing forms/reports/queries etc. and other users try to enter data we get messages saying exclusive access is required and any changes might not save properly.
Obviously there is an issue of useability because we have to hollar at each other to close forms so someone can do something.
I have a feeling someone is going to say I need a separate front-end on the user machines so users aren't working directly in the database, however I am no where near fathoming creating a VB front-end, at this point.
How can I fix this issue without creating a front-end? Do I need a server? Any ideas?
you have to do it with everything you change, not only Forms
ASKER
any other options? because i still need to notify the users prior to importing. would be nice to be able to seamlessly edit while users enter/view data.
what would it take to allow seamless object editing and data entry/view?
what would it take to allow seamless object editing and data entry/view?
The problem is caused because you are making changes to the design of the forms/reports/queries etc.
Yes the way to solve the problem is to create a frontend-backend setup. This is not difficult to do though
Make a backup copy of your database first then
Tools>Database Utilities>Database Splitter
Basically this creates on backend db with all the tables which become linked tables in the front end
Then when you can work on a copy of the front end db and cause far less disruption. Changes to the backend will cause disruption but these are generally less time consuming.
Perhaps a better approach would be to have a development front and back end. This way you can try out dummy data without upsetting anything. Then when you want to update the working version just replace the front end of the working version with the dev front end. You will have to get everyone out before you do this though but only for a minimal amount of time. Of course if you have made changes to the back end will need to be carried out on the working backend with no other users logged in also.
Hope this helps
Steve
Yes the way to solve the problem is to create a frontend-backend setup. This is not difficult to do though
Make a backup copy of your database first then
Tools>Database Utilities>Database Splitter
Basically this creates on backend db with all the tables which become linked tables in the front end
Then when you can work on a copy of the front end db and cause far less disruption. Changes to the backend will cause disruption but these are generally less time consuming.
Perhaps a better approach would be to have a development front and back end. This way you can try out dummy data without upsetting anything. Then when you want to update the working version just replace the front end of the working version with the dev front end. You will have to get everyone out before you do this though but only for a minimal amount of time. Of course if you have made changes to the back end will need to be carried out on the working backend with no other users logged in also.
Hope this helps
Steve
This will not work on the FE/BE either,but what is happening in the FE/BE is that each user will have his Forms/Reports on his/her PC, so you can do the changes on your own pc,
BUT
when you want to update the users Forms/Reports (FE), they have to be logged out too.
jaffer
BUT
when you want to update the users Forms/Reports (FE), they have to be logged out too.
jaffer
ASKER
Stephen, this is obviously the route i need to take....you mentioned a development front/back end, does this mean make 2 copies of the database and split both copies (then delete or make the original unsplit database a backup) then naming one development and one working (or whatever i want to name it) ?
Make one split which will give you a front end and a back end.
You could use this as the working dbs
Then make copies of the split versions and use them for development purposes.
Steve
You could use this as the working dbs
Then make copies of the split versions and use them for development purposes.
Steve
Hi Jaffer,
I would think that even if the the development front end db is linked to the same back end that other users are using there would not be a problem. Of course if other users are using the dev front end there would be a problem. Isn't this correct?
Steve
I would think that even if the the development front end db is linked to the same back end that other users are using there would not be a problem. Of course if other users are using the dev front end there would be a problem. Isn't this correct?
Steve
I had this same problem with my adp project. The way I solved it was by writing a little version control system using an external visual basic program. This launches at startup on the user's machine and hides in the system tray. It checks the back end for the latest version of the front end (which is a compiled ade in my case, it would be an mde in yours) via the builds table (which you have to put a new entry in for each new build). If the current build is earlier than the latest found on the db, it gets the newest build from the share and caches it locally. This method takes a little time to implement, but it is beautiful when it is done.
I forgot to mention that you launch by clicking the tray icon and that's when it checks for the latest version
if you know your vb pretty well I can send you the source code for my version control, but it is pretty involved and will take some major tweaking to make it work with your situation
if you know your vb pretty well I can send you the source code for my version control, but it is pretty involved and will take some major tweaking to make it work with your situation
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is an interesting link about the same issue
https://www.experts-exchange.com/questions/21079020/Multi-User-MS-Access.html
https://www.experts-exchange.com/questions/21079020/Multi-User-MS-Access.html
ASKER
jkorz, id love to implement your version control, however i would not be able to because im not a programmer....i found a link to a version control system off the shelf from FMS Inc. - http://fmsinc.com/Products/startup/index.asp
jjaffer, appreciate the link, but a tad over my head at this point
I think im gonna try the splitting approach first, thanks stephen
jjaffer, appreciate the link, but a tad over my head at this point
I think im gonna try the splitting approach first, thanks stephen
onestopfinancial
Thanks for the points
and good luck!
Steve
Thanks for the points
and good luck!
Steve
you cannot edit and add data at the same time.
jaffer