Microsoft Jet database engine NIGHTMARE!!

[jones54]

Hi,

I have been having intermittent problems with an MS Access 2000 front-end application linked to a SQL Server 2000 database recently.

From the switchboard a user was sometimes getting "There was an error executing the previous command". When she closes the application and opens it again it works fine for a little while - then the error occurs again.

I removed the generic error handling code from the code for the Switchboard form and I got the error message: "The Microsoft Jet database engine cannot find the input table or query 'Switchboard items'. Make sure it exists and that its name is spelled correctly."

I have been searching this forum and the web to find out what the cause of this error message is but I cannot find anything to go on or to try that might help get rid of this problem.

Does anyone know why this error occurs? Any idea how to stop it of happening? Or how I might troubleshoot to get further information?

Note I have given each user their own copy of the front-end to the database and only 1 user is experiencing problems. I have given the user a new mde file but this hasn't resolved the problem.

Any ideas or suggestions would be greatly appreciated.

Many Thanks

 

[LittleSmudge]

'Switchboard items' should be a table resident in the front end database ( a local table ) unless you have move the data out to the SQL Server db. If that is still true then the fault won't be with the ODBC link.

Are you running this on Windoz2000 and has the user got Automatic Updates enabled ?

Has the Rollup patch for SP4 been implemented ?
This thing is known to create all sorts of obscure faults in Access dbs ( even the supposedly fixed 2nd edition of it )




G LS

 

[smedvid]

I've had similar issues in the past where (1) user is having issues and the other dozen are A-Ok. My typical approach is to have MS Access re-installed on the troubled PC. It has always solved my problems. In my case, we have Access-97, Access-2000, Access-2002 (XP) and Access-2003 on all corporate PCs. So, I suspect if you have multiple versions, it could be a cross version or system library file issue. htwh,

Steve Medvid
"IT Consultant & Web Master"

http://www.saveourfarm.com

Chester County, PA Residents
Please Show Your Support...