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

How to Allow Multiple Users to Open Access File

100+
P: 124
I have an Access project on a shared network. I found that if a user is already in the app, no one else can access it. How do I allow multiple users to access the app at the same time?
Jun 29 '10 #1
Share this Question
Share on Google+
7 Replies


missinglinq
Expert 2.5K+
P: 3,532
A multi-user Access database simply has to be split, with the back end, with tables/data on a shared and a copy of the front end, with all other objects, on each user's hard drive.

Is this app split?

Linq ;0)>
Jun 29 '10 #2

thelonelyghost
100+
P: 109
It depends on the file format, from what I understand. MDB is horrible if you want it to do more than store information for one user to access. If you want to create an interface that multiple users can access simultaneously, I'd suggest using a server (MySQL is free for non-commercial use) and some scripting language (PHP works well with MySQL). It's not too difficult to learn and, if your web host doesn't support MySQL or PHP, there are plenty of free ones that do. PM me if you would like suggestions. I just went through that search and those same issues myself. w3schools puts out some excellent hands-on tutorials for PHP and SQL, also free.

If anyone else has a suggestion, I'm interested as well.
Jun 29 '10 #3

100+
P: 124
@missinglinq
The app is a .adp with a sql server db. The app must remain on the Citrix server so that it has a connection to the sql db so I can't distribute it to each user's workstation.
Jun 29 '10 #4

Jim Doherty
Expert 100+
P: 897
@bullfrog83
If on a trusted network (LAN/WAN) ADP Project files are best distributed to the user and can (but not necessarily or vitally) be stored in their desktop profile (copied down to their profile when they login to the domain).

The inbuilt connection to the SQL server when using ADP files is via 'Universal Data Link' so it matters not what PC they log in to they can always access the SQL Server concerned provided of course the SQL server is visible on the network and the relevant network permissions are set for the user via windows groups etc.

If you are storing a single ADP file on a citrix box and accessing a single ADP file through a citrix image to the desktop then all you are basically doing here is transferring a 'visual image' of what sits on the server to the client. This gives the illusion of speed and has been used as a strategy many times over to get around the poor performance issues inherent with MDB files over a wide area network.

Basically with Citix everything is being done on the server INCLUDING the operation of the ADP file. If your strategy is to allow many users access to a single ADP file over a citrix connection then your strategy needs to change to fall in line with the SPLITTING principle where data tables are in a backend (this case SQL Server) and frontends given to each user.

IMHO if you are on a closed network then I see no reason (unless of course there is one, in which case I will pretend I saw it :) ) why distributed ADP files would not perform for you over a 100mbps wide area network (or preferrably ADE files which makes better distribution sense given the footprint is smaller...stripped out code and lighter weight and less tamperable )

If your application is well designed harnessing optimised stored procedures and calling only the data it needs to the client from the server and so on... then performance should not be an issue. (ie not the typically unthinking SELECT * FROM TheLargestTableInTheUniverse so that when it hits my client machine I can merely just 'add' a record)... if you get the idea.

Sometimes I wonder if apps are merely put on a Citrix Server simply because someone says "Huh Access? ohhhh throw it on the Citrix box!" because of some perceived notion that it is likely to be the MDB performance problem.........It is not the same beast!
Jun 30 '10 #5

100+
P: 124
@Jim Doherty
OK, I no longer have a problem with more than one user accessing the app but now, if a user logs on and someone else is already on the app they get the message: This database has been opened read-only. You can only change data in linked tables. To make design changes, save a copy of the database" and then there's a Save As button. Now, I don't have a problem with the message as I only want users to make changes to the data (I plan on writing some xml to create my own ribbon that removes a lot of design features). However, I don't like the message appearing, especially the Save As button. How do I make it go away?
Jul 6 '10 #6

Jim Doherty
Expert 100+
P: 897
@bullfrog83
Does each user have their own distributed copy of the frontend now or are many users accessing a single forntend file? You really do have to distribute this so that each user connects to their own file and not have many users accessing one single frontend file
Jul 6 '10 #7

100+
P: 124
@Jim Doherty
I'm not sure how I can go about this. If I distribute a front-end copy to a user's desktop, Access is unable to connect to the database. Our SQL server and Citrix servers are outsourced so we have to log onto our remote-host vendors shared networks in order to have access to the sql server. I'll have to investigate with them.
Jul 7 '10 #8

Post your reply

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