runtime error, application shutdown

  • Thread starter Thread starter mollytaram
  • Start date Start date
M

mollytaram

I have some runtime users getting a runtime error and app shutdown
when opening a data entry form that I created from an Access 2002 db.
The form opens in data entry mode, and has several fields with default
values, including one which defaults to a fiscal year function that I
created. I am new to runtime, but have tested this on my own pc with
only runtime installed, and it works fine. When my client opens it, he
gets the error/shutdown. Any ideas on the possible differences in our
pcs/programs which would make him get the error, but not me. VERY
FRUSTRATING as I am across the country and can't look at his system
first hand, and don't even know what to ask to see what might be
causing this difference. thanks for any help you can offer...
 
Do you have error handling for all procedures (subroutines and functions) in
the application that you are sending out to your client? I *think* an
unhandled error can cause a runtime app. to shut down, as you have described.

Is the run-time app. a .mdb or a .mde file? The first thing I would check
for is the possibility of one or more references marked as MISSING. Here are
two excellent papers on this topic:

Solving Problems with Library References (Allen Browne)
http://allenbrowne.com/ser-38.html

Access Reference Problems (Doug Steele)
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

If your app. is distributed in the compiled .mde form, then it's going to be
a lot more difficult to track down a missing reference. You may need to
temporarily install your source .mdb file on the client's PC. Also, check
that any references that you have included are actually needed. It is best to
starve the included references listing. Make a back-up copy of your .mdb
file. Then remove one reference at a time, clicking on the OK button to
dismiss the references dialog. Make an attempt to compile the VBA code (Debug
| Compile ProjectName), where ProjectName is the name of your VBA code. If
you do not get a compile error after removing a checked reference, then you
did not need that reference.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
 
http://msdn2.microsoft.com/en-us/library/aa167800(office.11).aspx
Basics for Building Microsoft Office Access 2003 Runtime-Based Solutions
(Principles remain pretty constant between versions)

Article includes instructions on how to create a shortcut that will run an
app in runtime mode for testing purposes.

"...have tested this on my own pc with only runtime installed.." is not
something I would trust 100% unless I had scrubbed the registry between
installations.
 
Back
Top