Have an access database with a front and back end.
Front end holds forms etc and sits on each local pc and the backend sits on a network server.
Most of the users are working ok bar 2 they recieve compile errors.
When the database starts it runs an autoexec macro that basically checks version tables in the front and back end to make sure they corrispond. If they don't the user is prompted to update the database.
When this autoexec macro runs the error occurs and the debug immediately points to the statement
Set rstVerTabFE = CurrentDb.OpenRecordset("Version")
Set rstVerTabBE = CurrentDb.OpenRecordset("VersionBackEnd")
and highlights the currentDB funtion.
If I remove the autoexec the same happens when the user hits another process that uses the current DB function
I've checked references and nothing is missing.
Its appear to be pc specific as if I try to logon to the database on the pc I get the same error yet I work fine any where else
Any ideas?
Front end holds forms etc and sits on each local pc and the backend sits on a network server.
Most of the users are working ok bar 2 they recieve compile errors.
When the database starts it runs an autoexec macro that basically checks version tables in the front and back end to make sure they corrispond. If they don't the user is prompted to update the database.
When this autoexec macro runs the error occurs and the debug immediately points to the statement
Set rstVerTabFE = CurrentDb.OpenRecordset("Version")
Set rstVerTabBE = CurrentDb.OpenRecordset("VersionBackEnd")
and highlights the currentDB funtion.
If I remove the autoexec the same happens when the user hits another process that uses the current DB function
I've checked references and nothing is missing.
Its appear to be pc specific as if I try to logon to the database on the pc I get the same error yet I work fine any where else
Any ideas?