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 / Multiuser / Networking / October 2005

Tip: Looking for answers? Try searching our database.

Can't open shared database in design view?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Pamela G - 28 Sep 2005 12:55 GMT
I have a little problem with our shared database.  It's up on a server & is
shared by several users (about 6-7).  I can launch the database fine, by
double-clicking it, but as soon as I try to launch it while holding down the
shift key (to get into design view), it won't  open at all.  Once I attempt
this, the application itself won't even launch - it just seems to not respond.
It doesn't even show in the Task Manager.  Only way I can get to it again is
by rebooting.  I can get into design mode at least once, it seems, but
thereafter the thing won't launch at all.  Any ideas?

Thanks.
Pamela - 24 Oct 2005 16:35 GMT
This & other issues I have posted recently were all related to the same thing
- the use of conditional formatting in subforms (Access 2002, the mdb file is
in 2000 format).  

MSACCESS.exe was found to be running under the Processes tab in Task Manager
on the affected workstations.  Sometimes there would be multiple instances of
MSACCESS.exe because of this.  This was my first clue & I was able to isolate
the application (one of two with sub forms).  Armed with this knowledge, I
searched this forum and found the answer.  I removed the conditional
formatting & the problems went away!

Symptoms we had were:

1)  Users unable to open mdb file by double-clicking after opening & closing
the offending application (workstation thought Access was already running).
2)  Only way to open .mdb file was by opening Access on the workstation, then
opening the mdb file.
3)  .ldb file persisted even after all users closed out of the Application
(because the process was still running)
4)  Other Access Applications started "misbehaving" (would not open once
offending App was closed)
5)  Screaming, multiple phone calls,  and hair-pulling

As a side note:  it was this forum that solved the riddle.  I am fairly new
to Access & have found this forum to be a great resource.  (I am more
familiar with Oracle Forms & Reports).  

Thanks!

>I have a little problem with our shared database.  It's up on a server & is
>shared by several users (about 6-7).  I can launch the database fine, by
[quoted text clipped - 6 lines]
>
>Thanks.
 
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.