Fixing Bugs in Run-Time Version

[SC ChiefsFan]

I am fairly well versed in Access/References/etc, but trying to work out bugs
on a PC with run-time version only. The app works fine on most PC's (that
have Office) but my test PC that doesn't have Office has "issues" -
calculated fields using the "format" and "date" functions aren't working.
Seemingly a simple fix...

But since it's in run-time I can't determine what references are broken.
Any suggestions on determining which files I need to update/repair? I've
already downloaded updated MDAC, Jet 4.0, and even VB run-time on the test
PC. None have worked.

FYI, my development PC is XP/Office 2000 SP3; the test PC is Win2000 (No
Office Installed).

 

[Rick Brandt]

I am fairly well versed in Access/References/etc, but trying to work out bugs
on a PC with run-time version only. The app works fine on most PC's (that
have Office) but my test PC that doesn't have Office has "issues" -
calculated fields using the "format" and "date" functions aren't working.
Seemingly a simple fix...

But since it's in run-time I can't determine what references are broken.
Any suggestions on determining which files I need to update/repair? I've
already downloaded updated MDAC, Jet 4.0, and even VB run-time on the test
PC. None have worked.

FYI, my development PC is XP/Office 2000 SP3; the test PC is Win2000 (No
Office Installed).

Open a new blank file and then look at the references. Then look at the
references in the MDB you used to create your distributed app. ANY additional
references are likely the culprit. In most cases there is no reason to include
any references other than the default ones and instead use late binding for
manipulation of external libraries. Then you avoid nearly all of the these
issues.