Question Issues / Problems with Access 2010 conversion

[txgeekgirl]

Has anyone had any conversions issues relating to switchboards in Access 2010?

We have 2 DBs NOT on our DB Server - works off a drive share. These are 2003 DBs that are now running in 2010 because we've upgraded user machines.

I made some changes, built new reports, queries, and forms. I made the changes in the switchboard. For me - as DBA and a Domain Admin, it runs fine.

I copied and renamed the DB for End User use and for all (including myself) had Internal Object Could Not Be Found or Unable to Execute Command errors for everything.

I was able to clear mine by running the queries, forms, and reports from the back end one time and then the switchboard worked again.

Researching the issues online to fix End User machines, the "fix" was to run Compact & Repair from the EU Machine and unjoin and rejoin references. I did this and still have the same issue.

Anyone have these same issues? If so, What is the fix?

 

[gemma-the-husky]

Is this a standard A2003 8-item MS switchboard, or one of your own devising?

 

[txgeekgirl]

The only changes we made to the swithboard was to make it a 16 field instead of 8. (2 columned SB) Other than that it is standard. I also checked the Handle_click code. Even cut and paste the code from the prechange copy because the Switchboard code didn't change. Just listings in the Switchboard table.

 

[gemma-the-husky]

I prefer to stick to A2003, although I have both A2007 and A2001. I Just hate the "fixed" database window navigator, but I have no issues with my switchboard code.

Yes 8 items isn't enough is it? I have added a fair few other things to my switchboards. Check locale, check screen resolution, validate connection. etc etc. I also changed the standard cryptic (and unhelpful) "there is an error executing the command" to something more meaningful.

However, is it possibly something to do with trusted sources, and the code not running at all. Others have mentioned this sort of issue as a general "perhaps" in A2007/A2010.
I tend to set macro security to low, and thereby avoid all trust centre problems

Try putting a breakpoint in the switchboard open event - see if it runs the code at all.

 

[txgeekgirl]

Seems like everytime they "improve" a version, they disregard the actual people who develop for use.

The whole Enable and Make this a trusted Document crap is just that - CRAP. I hate having to enable editing on EVERY spreadsheet and Word Doc I look at.

I think if the switchboard code were defective it would be defective for all and I did get mine working.

I did throw it up on the DB Server and will try a connection to that when my main EU gets back from lunch.

 

[boblarson]

I think if the switchboard code were defective it would be defective for all and I did get mine working.

The trusted location/document is a PER USER setting so each person has to have that database location set to be a trusted location or trust the document for the code to run. You can have it set as a trusted location and so it will run for you but for someone else it won't if they haven't set that location as a trusted location.

 

[txgeekgirl]

I know - which is why I personally went over to the EU machine yesterday and untrusted all of her documents and opened this DB and re-enabled - re-trusted. I even made her an Admin on her machine. Still the same issues.

 

[boblarson]

I know - which is why I personally went over to the EU machine yesterday and untrusted all of her documents and opened this DB and re-enabled - re-trusted. I even made her an Admin on her machine. Still the same issues.

Well, then the code should be running (and as Dave asked) did you verify that it was by setting a breakpoint and seeing if it stopped at the breakpoint in the code? So, if the code is running then we can cross that item off the list for troubleshooting.

 

[txgeekgirl]

Well - here's the fix for running a 2010 database from a non-server shared location where it's using the users load of Access... You have to unlink all tables, uncheck all references and compact and repair, close, open..... Then reinstall references in the VBA and relink the tables for that user.

Her two DBs will be moved to a server tonight!