App runs on one PC but not another

[Peter Moffatt]

I have a holiday accommodation booking application set up to run under
Access 2000 Runtime. A client has three PCs all running Windows XP with
similar settings. The app runs on two of these machines but fails on
the third. It starts correctly, but fails while entering a new booking.
Customer name, arrive and depart dates are entered, with date format and
input masks specified in the property sheet. Accommodation category and
charging season are selected in combo boxes, and an error occurs at the
point where another combo box is about to display a list of available
units. The error message, with an exclamation mark on a yellow
triangle, is:

"This expression is typed incorrectly, or it is too complex to be
evaluated. For example, a numeric expression may contain too many
complicated elements. Try simplifying the expression by assigning parts
of the expression to variables."

The Help button identifies this as Jet Error 3071 and says that it is
trappable via the Error object. VB Help refers to the Error object in
relation to ADO and the Connection object and says that Visual Basic
users will need to retrieve error information from the Error object if
there is no valid Connection object, but does not make it very clear how
to do this. The error does not seem to be trappable by means of 'On
Error goto' and the Err object, or the Form_Error procedure.

The only other time I have seen this error message is when manually
entering a date parameter to a select query and entering the date
incorrectly (enclosed by #.......#). This made me suspect that the
problem might be something to do with Windows date format settings, but
I am told these are the same on all three machines. I also believe it
is possible that in view of the circumstances of the error, the error
message displayed may in fact have nothing to do with the real nature of
the problem.

Can anyone help with trapping the Jet error, has anyone come across a
similar problem, or does anyone have any idea what might be causing it?
Thanks for any suggestions.

Peter Moffatt.

 

[Guest]

Peter,
I don't know if this is related or not, but I had a similar problem. My app
would run on most PCs, but a few failed. Turned out the problem was that on
the failing machines, the DLL required for one of the ojbect libraries I was
referencing were not installed. We installed the offending DLL and
everything worked fine. In my case, it was not under Run Time, but just an
mdb the user was instructed to copy from a server folder.
If you are using run time, then I assume you have the 2000 Access
Developer's Kit. It has been a while since I used that, but as I recall, you
could include any files you needed in your setup.exe build. My fuzzy memory
seems to recall there is an option to include all referenced libraries, but I
may be halucinating again.
I hope this may be useful information.

 

[Guest]

Peter,

This may be a repeat, There was an error posting, but the shor version is,
check to see that all the required DLLs are installed on the offending PC. I
had a similar problem, and that was the cause.