You've just identified the reason that a lot of developers shun ActiveX controls. You need to
make sure that each target machine has a properly registered copy of all controls. Usually, it is
best to distribute only a compiled .MDE version of the database when one uses ActiveX controls.
The reason is that most users will only have a run-time license, as opposed to a design-time
license. A run-time license does not allow for any design changes to the form or report that
includes the control, including behind-the-scenes attempts to update objects and controls via the
Name Autocorrect mis-feature.
Suggest you develop in the language version that you will distribute in, and distribute only as
the .MDE version. Make sure you have the rights to redistribute run-time versions of your ActiveX
controls. These controls usually require settings in the registry, so they need to be properly
registered (not just copied to the target machines).
Tom
__________________________________
Thank you for your help.
It seems working, as some errors such as "There is no object in this
control" were no longer appear when open VB editor, but some ActiveX
controls which are not native from Access still generate errors.
Anywhere, thank you for solving the first problem.
Happy New Year!
gz
__________________________________
Have you tried the undocumented /decompile switch on a *COPY* of your database? Compact the
database and try recompiling from the debug menu (Debug > Compile DatabaseName). Running
/decompile and compacting should discard any compiled P code, which may not be language
compatible.
Start > Run: msaccess /decompile
and then open the affected database and click on Tools > Database Utilities > Compact & Repair
The above command will work, as long as you don't have multiple versions of Access installed on
the same machine.
Tom
__________________________________
Hi, I found if a database created on Chinese version windows 2000, it cannot
work on English version windows 2000, when there are VB codes. If the
database created on English windows 2000, it can work on Chinese windows
2000, but if the VB code are modified in Chinese windows, it cannot work on
English windows again. I installed Chinese version Office 2000 on both
operation system.
Does MS has noticed about this and had any patch for this problem?
Thanks!
