I got a problem I don't understand.
I am developing a VB application for a customer. On my PC's the application
is running OK, but on the customer PC the app hangs. When I look at the err
log I only got the message that the error nr is 0. Normally this line
appears only in my err.log when I forgot "Exit Sub/Function" before the
error handler. But this is not the case here.
I had the problem myself at the beginning of the project when I tested the
app on my test PC (On my dev PC the problem did not occur; everything worked
well there). The line where the zero error ocurred, tried to access a table
in a MS Access (mdb) database file. Since the referenced DAO was updated to
version 4 (MS Access 2000) and the database was constructed using MS Access
97, I changed the reference back to DAO 3.51. After that the zero error
disappeared until now.
Since I can only guess I has something to with a bad reference to a DAO
library; I don't know what is causing the problem however. Completely
reinstalling the app on the customers PC does not help.
I got the following questions.
First of all; how can a "zero error" act a as normal (that is a non zero)
error, by jumping form a valid line of code to the err handler like a normal
error? (Also the Err.LastDllError returns a zero.)
Secondly, what is the cause, so I can tackle this problem.
I appreciate any help.
Hans Heezemans
hh@iservi.com
www.iservi.com