I seen this happen with access97 when different versions of JET are on each
pc. This means in effect that your target computers have different software
libraries then your development computer. I can vouch for how incredibly
serous this can be, since my application was being used to determine "large"
advertising budgets based on sales figures from my reports, and wrong
numbers in this case could have caused money to be spent in the wrong way
(so, this is VERY serous issue).
Since the above is such a serous problem, then good developer realize that
it is ABSOLUTE important to ensue their clients install the correct service
packs, and also install the ZILLIONS of bug fixes contained in those service
packs (it will be silly to stand here and complain about a bug, but not have
ensured that you took time to install all the bug fixes!!).
For example, if you are running access97, then you need to ensue that all
pc's (of course your development pc is most important). have all the latest
updates.
you need to install
sr1
sr2b
jet25sp3.exe
You MUST install all of those updates...and especially the updates to JET.
If you are running a latter version, then again you need to ensue the
updates (with the bug fixes) are installed. And, as the other poster
mentioned, you might want to test/check the date/regional settings, as that
can often mess up your queries with dates (again, this only happens if you
did not take the different date formats into consideration during your
designs).
Last, but not least, broken references can also cause this. Does the
code/application compile correctly on the target machine? (can you turn the
mdb into a mde on the target pc ok?).
