Microsoft Access 2000 In A Multi-User Evironment?

[VoodooRage]

Does anyone have a quick and dirty (or not) primer for taking an Access 2000 database and placing it in a multi-user environment. I have a Database that if fully functional, formally normalized, all the controls are programmed just the way I intended. The app is finished. How do I or what can I do to implement the app utilizing a back end containing the tables on a LAN with a front end MDE file accessing the back end. Specifically what pit-falls to plan/program for and how to update the controls in the MDE on a periodic set frequency just anything someone who has not ever implemented a multi-user Access 2000 database might need to know.

Thanks,

 

[gusbrunston]

[tt]
Hi:

Splitting the database into front end and back end is relatively simple. In fact, there is a utility that does it for you.

There is nothing particularly touchy about the multi-user environment--each workstation has a copy of the Front End (and a licensed copy of MS Access) and accesses the back end (data) over the LAN. The back end machine or server does not need a copy of Access.

The area in which I have encountered the most problems is not with the access application, but with the design and maintance of the LAN. If you have a stable, well-designed LAN, then you'll avoid most of the problems I had.

Another Godsent utility came with the discovery of a neat "Autoupdater", which allows me to place the most recent revision of the front end in a directory on only one box. Then each user gets the most recent version automatically copied to his workstation when he opens the application. I used to have to go from workstation to workstation to install the revisions. Now the latest revision spreads (like a worm, I guess) to the other workstations. If you're interested, I'll look up the URL where you can download "Autoupdater" and the instructions.

Also, when you've got multi-users, you better have a good backup plan. Any of our users can back up data with a button, the backup copy of the back end is date and time stamped, and saved on a dedicated USB 2.0 external drive, and eventually moved off-site to

http://www.xdrive.com.

Also, you should back up the versions of the front end. You might have to go back three or four versions and get a query or a form which you thought you could safely delete. Know where to get it.

Hope this is helpful.

[tt]Gus Brunston - Access2000(DAO)
Skill level based on 1-10: 7, on the way to 6, and beyond!
Webmaster: www.rentdex.com[/tt]

 

[JeremyNYC]

Splitting the database is very basic and very necessary. I use batch files to do the updating of the front end on the PC. I've written up the process on my website. You'll also want to consider using security. If you do use security, PLEASE don't try to reinvent the wheel: there's already a security system built into Access. It's nowhere near bullet proof, but it's good enough for most applications. There's some stuff on this topic on my site as well.

Also, the next time you build an application, build it with final usage needs in mind from the start, so that you can be testing the speed of your queries over the network all along. There will be a lot less going back and tweaking things that way.

Also, you might want to run out and get a good book on the topic, if you're going to be doing a bunch of this. The one I always recommend is the Access [version number] Developer's Handbook.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.