Switchboard trouble

[Guest]

I have two Access databases with switchboards, one new database and one old
database. The old one, without having had any changes made to it, started
giving me a run-time error on startup, before seeing the switchboard. I can
hit the end button, and it will show me the minimized database, which I can
expand and work with normally. If I hit the debug button, it brings me into
some VBA code for the switchboard, cide I did not write.

the same thing happens with the new database, once I set it up to run with a
switchboard. It occurs wether I use the AutoExec macro method or the Startup
dialog method of displaying the Switchboard.

Any suggestions?

 

[Arvin Meyer]

What happens if you use another form in your startup? If that works, delete
your switchboards and either build new ones, or just build a standard menu
form with buttons that open other forms or reports.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Larry Daugherty]

--
-Larry-

 

[Larry Daugherty]

You should take note of the run-time error number and any verbiage in the
error message. When you hit the debug button it should leave you in a
module with a line of code highlighted. If not, hit F5 to run and it should
repeat the error message and halt with the line of code that has a problem
highlighted.

Post back with the line of code and the error text inserted into your post.
In the meantime, you'll be at a good starting point to start your own
troubleshooting.

HTH

 

[Guest]

Thanks, Larry. The error number is '-2147221164(80040154)'
ther verbiage is "Class not registered"

When I open the debugger, the highlighted code is:
rs.Open stSql, con,1 ' 1=adOpenKeyset

This is not code I wrote for my database, but is apparently code generated
when using the Switchboard Manager. If I try to open the switchboard as a
regualr form, I get the same thing. I can open the switchboard Items table,
but nothing appears out of the ordinary. Again, the perplexing part is that
this happened on two separate databases, one new, and one which had been
operating using the same switchboard module without any problems for almost a
year.

Might this be related to an update, either for Office or for Windows, which
might have been pushed out from out IT department recently? I am one of the
few people in our agency who uses Access, so it is conceivable that this
happened a while back, but I am the only one who has noticed it.

 

[Larry Daugherty]

It's already beyond my ken.

The updates pushed out by your IT department could have fractured something.

Open a module for design and then click Tools|References. If any of the
references is marked MISSING, uncheck that reference and then check it
again, close the references dialogue and compile your application.

Another thing to be wary of is whether your IT department is propagating all
of the relevant service paks.

If you still have the problem, include your OS and version(s) of Access in
your next post.

HTH