Wrox Programmer Forums
|
Access VBA Discuss using VBA for Access programming.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access VBA section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old August 8th, 2007, 10:35 AM
Registered User
 
Join Date: Apr 2005
Posts: 352
Thanks: 14
Thanked 0 Times in 0 Posts
Send a message via Yahoo to rupen
Default Multiuser Access application.

Hi,

I have a multiuser application in access. the problem is when a user uses the application it gets locksed and hence i can't go over and do any changes, so have to mail all users to close the application and do whatever changes are required and mail again to start using bla bla...

Any idea how could i do changes while users are still using my application????

Thanks in advance...

Rupen Anjaria.:)
------------------
It is not difficult to be on TOP...It is difficult when you carry Truth,Commitment and Transparency with you.
 
Old August 9th, 2007, 06:54 AM
Friend of Wrox
 
Join Date: Mar 2004
Posts: 3,069
Thanks: 0
Thanked 10 Times in 10 Posts
Default

There are best practices for multi user apps with Access.

Normally you can split the database and keep the tables in a common back end in a commonly mapped network drive, and then give users a link to a front end stored on a network drive, OR give each user a copy of the front end. The users open the common front end which accesses the common back end, or their own copy of the front end. The problem with the second solution is that you have to get each user to manually save over the old front end when you have an update of the new front end. With the common front end, the users' each have a shortcut on their desktop, and they don't even need to know updates are being made to the front end.

If you want to develop, take a copy of the common front end and put it on your desktop. Then paste the revised front end to the network folder in the evening.

Developing the back end can be done on the fly, but be careful of making substantive structural changes when users are working.

Did any of that help?

mmcdonal
 
Old August 10th, 2007, 06:46 AM
Registered User
 
Join Date: Apr 2005
Posts: 352
Thanks: 14
Thanked 0 Times in 0 Posts
Send a message via Yahoo to rupen
Default

When i will paste revised copy, if someone is already using it, can create a porblem?

Rupen Anjaria.:)
------------------
It is not difficult to be on TOP...It is difficult when you carry Truth,Commitment and Transparency with you.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Access application Gajun Access 3 September 13th, 2007 08:36 AM
Grid View in Multiuser Environment contactajo ASP.NET 2.0 Professional 0 June 6th, 2006 10:32 AM
VB .Net MultiUser Environmnet? SolverSurfer VS.NET 2002/2003 1 June 30th, 2005 05:39 AM
Multiuser access 97 runtime error anonymous1 Access 0 December 24th, 2004 09:48 AM
Multiuser Considerations In SQL devrishi SQL Server 2000 15 August 12th, 2004 09:30 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.