Runtime Error

danireh

New member
Local time
Yesterday, 18:23
Joined
Mar 12, 2009
Messages
3
Hi,

Could anyone please help me in resolving the attached runtime error. I am using vba code, to generate some outputs on the forms, its working fine in my database, but when I am creating an installable package with accessruntime.exe, to install it on a system running Access 2003, IF user try to open a form consisting any VBA Code, the attached error is appearing and closing the applicaiton. How could it be tracked, so that would be able to generate the same outputs on systems without Access 2007,
 

Attachments

  • Runtime Error.JPG
    Runtime Error.JPG
    20 KB · Views: 173
welcometoawf.png


When using the Runtime you need to do several things (the first is probably the thing you need for this) -

1. You need "bullet-proof" error handling. You are possibly getting a runtime error that needs to be handled so your program does not shut down.

2. You need to include any menus or ribbons for your users.

3. You need to have a start form defined as it will not have an interface otherwise.

So, it can be a daunting task to figure out what is causing a problem as far as runtime errors go but you need to include error handling on almost everything so that you can catch those and deal with them. Have you done that at all?
 
Thanks for your response boblarson,

I am using switchboard form at startup, in my application.
This application is performing all the Access genertated queries and reports, and users are able to open/view forms and reports, for which there is no vba coding.

But as soon an event coded in vba is executed this error is appearing.

I tried the following code to catch the error but its not working as well.


===========
Sub Command38_Click()

On Error GoTo Err_Command38


' my code is here


Exit_command38_click:
Exit Sub

Err_Command38:
MsgBox Err.Number & " - " & Err.Description
Resume Exit_command38_click

End Sub

===========
 
Check to see if there are any compile errors. Go to the VBA window and then to DEBUG > COMPILE and see if it highlights anything.
 

Users who are viewing this thread

Back
Top Bottom