multiple users with access

[salmonella]

Resending this since can not see the first message I sent on the board

Is if possible to put an Access FE on a mapped network drive where multiple
users can use it at the same time from their machines?

I am using an Access FE and mysql BE and want to be able to update the FE by
simple changing the one copy instead of putting the FE on each machine.

At the moment once the first person boots it up on their machine, it becomes
a locked file and won't let others us the FE on their machines.

thanks,

 

[Klatuu]

Never, ever, under any circumstances, for any reason, share an Access FE on a
shared drive.
You are seeing only a small tip of the problems here. Updating the FE is
not a big issue; however, trying to recove a corrupt FE is. And you can bet
your lunch money a shared FE will suffer corruption.

There are a couple of easy ways to update an FE. First, you can search for
an Access Front End updater you can fold into your application. Here is a
link to one I lke:

http://www.autofeupdater.com/

There is also a very simple way that requires not code nor modification to
your existing application. It als has the advantage that you will never
suffer bloat and the likelyhood of corruption is almost nill. And if the FE
on a user's computer gets corrupted, the solution is to close the application
and re open it. How simple can that be?

The trick is that the icon on your desktop does not point directly to the
application. It points instead to a .bat file that does 3 things:
1. Delete the existing FE
2. Copies the FE file from a shared network folder to the user's computer
3. Launches the FE

All you need to do to update the FE is to put a copy in the location
specified in the bat file. The next time a user opens the FE, it will be the
new version.

When I first learned about this from a co worker, I argued the copy time
would make it appear slow to load. I did some "visual" testing and found
that for even a large app, it is very fast.

 

[salmonella]

Yes, I think you have the solution!!!!

many thanks!!!

 

[SoCal Rick]

DAVE: Wow, everytime I think I know a bit more about Access, someone comes
along with something that reminds me again about how little I know. I am
giving you a standing ovation for your "simple" answer -- .bat file. I
looked up .bat files in wickpedia and was fascinated. Any chance you could
give some sample code to accomplish the missing below:

There is also a very simple way that requires not code nor modification to
your existing application. It als has the advantage that you will never
suffer bloat and the likelyhood of corruption is almost nill. And if the FE
on a user's computer gets corrupted, the solution is to close the application
and re open it. How simple can that be?

The trick is that the icon on your desktop does not point directly to the
application. It points instead to a .bat file that does 3 things:
1. Delete the existing FE
2. Copies the FE file from a shared network folder to the user's computer
3. Launches the FE

All you need to do to update the FE is to put a copy in the location
specified in the bat file. The next time a user opens the FE, it will be the
new version.

When I first learned about this from a co worker, I argued the copy time
would make it appear slow to load. I did some "visual" testing and found
that for even a large app, it is very fast.

Where would I go to find out more about using an icon and link to a .bat
file to have better control over the front end of my Access database?
THANK YOU.
SoCal Rick

 

[Denise]

Does this work for Access 2007?

Never, ever, under any circumstances, for any reason, share an Access FE on a
shared drive.
You are seeing only a small tip of the problems here. Updating the FE is
not a big issue; however, trying to recove a corrupt FE is. And you can bet
your lunch money a shared FE will suffer corruption.

There are a couple of easy ways to update an FE. First, you can search for
an Access Front End updater you can fold into your application. Here is a
link to one I lke:

http://www.autofeupdater.com/

There is also a very simple way that requires not code nor modification to
your existing application. It als has the advantage that you will never
suffer bloat and the likelyhood of corruption is almost nill. And if the FE
on a user's computer gets corrupted, the solution is to close the application
and re open it. How simple can that be?

The trick is that the icon on your desktop does not point directly to the
application. It points instead to a .bat file that does 3 things:
1. Delete the existing FE
2. Copies the FE file from a shared network folder to the user's computer
3. Launches the FE

All you need to do to update the FE is to put a copy in the location
specified in the bat file. The next time a user opens the FE, it will be the
new version.

When I first learned about this from a co worker, I argued the copy time
would make it appear slow to load. I did some "visual" testing and found
that for even a large app, it is very fast.