Front-End linked to Back-End MS-Access database 1

[gwendon]

The way I was taught in a multi-user environment, was to setup a single MS-Access dB on the fileserver, then recreate as needed separate MS-Access dB's on each persons PC, linked back to the One MS-Access database on the fileserver.

But I find it works just fine, to eliminate these front-end databases, and simply have multiple users pull-up the One MS-Access database on the fileserver.

My question is: Do I really need these from front-end ,linked to back-end, databases for some reason I do not understand?

 

[psemianonymous]

It's a lot of incremental bonuses, including:

--ability to update the database painlessly. With a shared frontend, you have to get everyone off, make all changes, then, after all changes are made, THEN let everyone back in.

--In Access2000+, 'passive shutdown' problems with a shared frontend--no problem with multiple frontends.

--Reduced chance of corruption. In a specific instance, I was having problems with a citrix/terminal server app. I reduced the problem occurrence from a "instant problem" to a "weekly"/"semi-weekly" just by setting up multiple frontends on the personal folders on the citrix server. (The final solution: oplocks.)

--Speed - though this is a marginal benefit.


I think the most important aspects are corruption (minimize at all costs!) and the updating. If you're not having corruption issues (and can forsee the future and don't envision any), and you're not going to be doing much updating of the database, that's fine. Leave as-is.

But if you're doing fine, great. I wouldn't recommend regressing from multiple-frontends to shared-frontend.


Today is Tony Toews day for me. He has a page on the subject of splitting databases, and says pretty much the same thing I just wrote (but better, of course):

http://www.granite.ab.ca/access/splitapp.htm

 

[Hap007]

Dear foolio12,

Well said, I give you a Star.

It just amazes me that this same issue comes up again and again.

The easy way is to share a Frontend on a Server.
But... This shared method seems to:
1) Slows speed as number of users increase.
2) Increases chance for corruption
3) Makes new development more difficult

The best methods usually take a little more effort at the beginning, but ultimately save time.

Frontend on User PC, backend on the server gets my vote everytime. (Especially if you use Access 97)

Good Job,
Hap


Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Add-on Solutions
Access Consultants forum

http://www.tek-tips.com/groups/accessDevelopers