Switchboard error

[marnieg]

I am using Access 2007. I have had an application running now for about 1 year and now getting an error when user opens the database. (Have one for front end and one db for backend)

Here's the error message:

[FONT=&quot]The form name Switchboard is misspelled or refers to a form that doesn't exist.


Also, multiple users are accessing the database at the same time.


[/FONT]

 

[missinglinq]

Does your app actually have a Switchboard, or a custom Form named Switchboard? If not, has it had one at some point in time?

...Have one for front end and one db for backend...

...multiple users are accessing the database...

Are all users accessing a single Front End, or do they each have a copy of the Front End on their machines?

Linq ;0)>

 

[marnieg]

It is using the Switchboard manager and all users are accessing the same db. When the application opens they have the ability to see all the object types. When they get the error and click OK, it only shows the linked tables and queries. The objects for FORMS and REPORTS are missing.

The strange thing is they can be using the application for sometime then log out (which does a compact and repair) and then when they try going back in it causes the problem.

 

[missinglinq]

First off, having multiple users sharing a single Front End, sitting on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior, including the problem you're having, now! Multiple users simply have to work off of their own copy of the Front End!

Being in forced retirement, I spend 6-8 hours a day here and on other Access forums/newsgroups, and over the past seven years have seen dozens and dozens of reports of the type of set up you’re using causing these kinds of problems as well as massive data lose! The really insidious thing is that it can work for extended periods of time (as is your case) before the troubles begin! But once it does, they become chronic, recurring over and over and over again! You simply have to give each user a copy of the Front End on their PCs.

Secondly, Compact on Close is possibly one of the absolute worse features Microsoft ever added to Access! Ironically, C&R is a recognized cause of Corruption and should never be done without first backing up your file! In addition to this, in a well-designed Access database, there is simply no reason to do a Compact each time the app is closed.

Linq ;0)>