Hi Olda,
I would try repeating this experiment, using the Northwind 2007 database, to
see if the new computer has the same issue. Although I do not have any
experience with run-time installations, if my memory serves me correctly, you
need to ensure that you have proper error-handling for *ALL* VBA procedures
(functions and subroutines). Otherwise, run-time solutions will simply bomb
out to the operating system--that's how it has worked (or not worked) in the
past.
I'd also check the listing of references that you have included in your
application. Verify that any checked references are available, in the same
file path and with the same file version, as they are in your development
machine. Ensure that you do not have any extra references included, that are
not absolutely required. You can determine if a reference is required by
attempting to compile the VBA code after removing said reference (remove one
at a time, making a note of the name). If your code continues to compile
without any errors, then you simply did not need that reference.
Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________