Things That Work on One Computer and Not Another

[Guest]

So far, I've found two things in my Access application that work on my
corporate workstation but don't on some others (supposedly the same operating
system and application patch levels).

1) Form fields that get populated programmatically -- Two fields located in
the form detail section that worked fine on my (and other) machines demanded
values before the form would open on some machines. When I moved the fields
to the form header, the problem was no more.

Maybe they should have been there to start with, but it's very weird to me
why it worked on some machines and not others.

2) DTPicker (Class: MSComCtl2.DTPicker.2) object doesn't work on some of
these same machines.

Any ideas?

Thanks,
Bill

 

[John W. Vinson]

So far, I've found two things in my Access application that work on my
corporate workstation but don't on some others (supposedly the same operating
system and application patch levels).

1) Form fields that get populated programmatically -- Two fields located in
the form detail section that worked fine on my (and other) machines demanded
values before the form would open on some machines. When I moved the fields
to the form header, the problem was no more.

Maybe they should have been there to start with, but it's very weird to me
why it worked on some machines and not others.

2) DTPicker (Class: MSComCtl2.DTPicker.2) object doesn't work on some of
these same machines.

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.

John W. Vinson [MVP]