Fatal "Run-Time" Error

[bob bisquick]

I have an Access database that runs on a machine with a run-time version of Microsoft Access 2000, distrbuted by the original designers of the database. Several times I have designed other databases that function as reporting tools, they generate reports based on data in this original databse. This has been not a problem.

For some reason, on a new databse I have designed in this way, I can get it to run on my personal computer with a full version of Microsoft Access 2000, but when I place it on a machine with the run-time version of Access 2000, I get the following error every time the data base tries to run any code, other then open this from, close that form, etc...

Execution of this application has stopped due to a run-time error.
The application can't continue and will be shut down.

As soon as I click OK it shuts down.

It does not seem to be related to a specific command, meaning it happens everytime I try to run any code, regardless of what or where that code is, and regardless of how simple or complicated it might be.

It seems like there is something sitting somewhere in the database that the run-time version of Access does not like, but I'll be hornswaggled if I figure out what it is.

 

[ghudson]

You need to use error trapping in all your Subs() and Functions(). Runtime errors are fatal when a db is used in the runtime mode. The error trapping will also help you identify which routine is causing the problem.

Here is a simple error routine...

Private Sub bEmployeeData_Click()
On Error GoTo bEmployeeData_Click_Err

    DoCmd.OpenForm "frmEmployeeData", acNormal
    DoCmd.Close acForm, Me.Name

bEmployeeData_Click_Exit:
    Exit Sub

bEmployeeData_Click_Err:
    MsgBox Err.Number & " - " & Err.Description, vbInformation, "bEmployeeData_Click - Error"
    Resume bEmployeeData_Click_Exit

End Sub

 

[bob bisquick]

Thanks. That will take a little while to implement... a lot of subs.

 

[bob bisquick]

ghudson -

I have set up error trapping, as per your response, and I am still having the same problem (ie I get the same error with no info). I see several possibilities:

1) Despite your post, I set up error trapping incorrectly. I compiled the code, and eliminated all the typo type errors that access found. I do have a couple of subs and/or functions where I had a problem. With functions, does error trapping take the same format? What about Form_Opens and Form_Closes etc...

2) In order to make this database work, I need to turn on several references. To solve this problem for distribution, I distribute a folder withh all the reference library files I need, and you can then point to this file from within the database. I have tried this before and seems to work, although only with 2 or three references, this time I am doing it with 9. This shouldn't make a difference, but...

still perplexed...