Access 2010 runtime crashes my application

Question

My database application runs well on a full version of Access 2010 but crashes using run-time 2010.  The errors are numerous and a lot of the VBA complied code becomes unavailable.  Does anyone know how resolve issues with run-time 2010?

Answer 1

On the configuration with the runtime version, do you have trusted location set up?

Answer 2

Does your application include custom controls / activex controls that are not included in the run-time distribution package?

Answer 3

First thing, do a debug/compile in your database and fix all errors until it compiles without errors.

Second make the database into an .accde.

Thirdly, test it in run-time 2010.

If you still have problems, we can show you how to use a step-wise approach to track down and fix the errors.

---

Jeanette Cunningham

Answer 4

- Established trust locations

- Code Complies fine

- Saves to a .accde file without any problems.

- Work fine with tables included using run-time 2010

- Does not work when the database is split when running run-time 2010 - the data is accessible but all the queries and a lot of the code is disabled or breaks.

- Seems to be an issue with the split database

- This error only occurs with run-time.  The split database works fine with a full version of access

- The errors occur regardless if the split database is stored locally on the user machine or on a network.

- The error explanation is as follows:  "This error occurs when an event has failed to run because the location of the logic for the event cannot be evaluated. For example, if the OnOpen property of a form is set to =[Field], this error occurs because a macro or event name is expected to run when the event occurs".

 

Answer 5

Darn it!  Turns out it was a bad reference in the VBA project.  The compile didn't pick it up because the .dll file was on my computer where I do the development but not on the other user machines where I was installing Access run-time.  Of course, the error didn't tell me that...

Answer 6

It is a runtime bug, but Microsoft will not admit it. Perhaps the runtime should obtain a little break at the start and I've achieved with the Startup  form OnOpen :

Dim ref As Reference
Dim msgsve As String
    For Each ref In References
        If ref.IsBroken = False Then
         msgsve = "  :  " & ref.Name & vbCrLf & "FullPath:  " & ref.FullPath & vbCrLf & "Major:  " & ref.Major & " Minor:  " & ref.Minor & "-- OK " & vbCrLf & msgsve
        Else
         msgsve = "Miss..: " & vbCrLf & ref.GUID & "  --- ??? " & vbCrLf & msgsve
        End If
    Next ref
     MsgBox msgsve, vbInformation, "REF..........."

This break is sufficient to open the app.

Sorry for bad English

Roly..

Answer 7

Is there any run time error? Probably your file might have got corrupted. Anyways, you can repair access file using some third party software.