Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / SQL Server / ADP / June 2006

Tip: Looking for answers? Try searching our database.

Access Front End broke. Due to concurrent users?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mikal - 30 Jun 2006 16:44 GMT
I searched this forum but didn't find anything like this that looked like it
was particular to .ADP files.  Maybe that's because it doesn't matter what
kind of file you're using.  If so, I apologize for being bone-headed.

We (not me, I didn't do it) have a .ADP front end housed on a network drive.
It is the only copy of the front end in use for several concurrent users and
it broke--fortunately, there was a back-up copy available.   The data on the
SQL Server seems fine.  What appears to have happened is some of the controls
on the main form lost their connection to the fields in the underlying tables
and maybe some other stuff too.  We just replaced the bad file with the good
copy when we realized we had one.

Questions:
1.  Can having multiple users in a .ADP file do this?
2.  Are we likely to corrupt the data this way?  I'd bet on it in a .MDB file,
but I never used .ADP.
3.  Would compiling to .ADE files be any stronger
4.  Should we give each user his own copy of the front end and maybe password
protect the various front ends to enforce having the users open only their
own individual copies? (I think they're all going to have to reside on the
shared drive.  When I moved a copy off of the shared drive onto another
network drive I got the message that the front end was disconnected).

Thanks Beaucoup!
Mike

Signature

"We have met the enemy and he is us." -- Pogo Possum

Sylvain Lafontaine - 30 Jun 2006 18:47 GMT
In the same way that's much better to split a MDB database into a frontend
and a backend and give a personal copy of the frontend to everyone, each
user should have his or her own copy of the ADP file.  If you want to
compile to ADE, the compilations should be done separately on each user's
machine to make sure that you don't any problem with any difference in
versions of Windows, Service Packs and support files and libraries.

For you deconnection problem about locating copies out of a shared drive, I
don't understand it; however, it should be easy to reconnect them from the
File -> Connection menu.

Signature

Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

>I searched this forum but didn't find anything like this that looked like
>it
[quoted text clipped - 30 lines]
> Thanks Beaucoup!
> Mike
Mikal - 30 Jun 2006 19:12 GMT
Thank you very much for your reply and for confirming my suspicions.  Thank
you also for the re-connection information.  I didn't know that.

Mike

>In the same way that's much better to split a MDB database into a frontend
>and a backend and give a personal copy of the frontend to everyone, each
[quoted text clipped - 12 lines]
>> Thanks Beaucoup!
>> Mike

Signature

"We have met the enemy and he is us." -- Pogo Possum

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.