By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,705 Members | 1,795 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,705 IT Pros & Developers. It's quick & easy.

Changing Database Setup Mid-Stream

P: 10
I am using MS-Access 2003 with a split database on our server. I have the front-end in one folder and the back-end in another. I have the users using a shortcut to the front-end. Of course this restricts what I can do as far as development during the day while the users are online.

Can I implement the scenario where I put the forms/rpts/queries/etc on each user's local drive and point to the backend at this point? How would I accomplish this and keep the setup with the Jet Engine interface? I realize this was a major miss during my design.
Dec 6 '07 #1
Share this Question
Share on Google+
2 Replies


Jim Doherty
Expert 100+
P: 897
I am using MS-Access 2003 with a split database on our server. I have the front-end in one folder and the back-end in another. I have the users using a shortcut to the front-end. Of course this restricts what I can do as far as development during the day while the users are online.

Can I implement the scenario where I put the forms/rpts/queries/etc on each user's local drive and point to the backend at this point? How would I accomplish this and keep the setup with the Jet Engine interface? I realize this was a major miss during my design.

Yes you can, thats how it should have been setup. Just search on here for 'refresh links' you'll see plenty of references to this coming up.

The benefit of splitting being that each user has their own copy on their client machine. This allows you to continue developing on the frontend (your copy) without effecting anyone else. You then distribute the frontend to the users (logon scipt or whatever means suits you)

The connection to the backend database should be to a common share with all users having the same mapped drive letter and the frontend file placed also in a folder of a common name on each client so that any 'shortcut' you might want to use has a standard appearance and feel to it. Look at 'command line switches' in access and the use of %profile% within that if your frontend file is to sit in the users profile

I'm not so sure what you specifically had in mind by the 'Jet Engine interface' except suffice it to say that any frontend file runs under the usual retail installation version of Access on the client.

Regards

Jim :)
Dec 6 '07 #2

missinglinq
Expert 2.5K+
P: 3,532
As Jim said, this is how a multi-user app should have been set up to begin with! Multi-users on a shared frontend is one of the most commonly sited reasons for corruption.

Welcome to TheScripts!

Linq ;0)>
Dec 6 '07 #3

Post your reply

Sign in to post your reply or Sign up for a free account.