When I run VB4 setup for my application on other PC's, when the program
gets ready to finish the setup it gives one or more (depending on the PC)
messages about being unable to register OCX files.  Works just great on my
PC.

On one PC I just get the message for the CRYSTL32.OCX file.  On a different
PC I get the same message for COMDLG32.OCX, TABCTL32.OCX,
DBLIST32.OCX,DBGRID32.OCX, THREED32.OCX, GUAGE32.OCX and CRYSTL32.OCX.  I
have double checked that I have the appropriate DLL files and have included
EVERYTHING suggested by the setup wizard.  I have even downloaded a program
to tell me which files which DLL's I could be missing, and even including
everything in my kit cannot get this to work.

Does anyone have any ideas on how to find what I am missing?
Thank-you.

A bug in an earlier version of Microsoft Visual C++ falsely demands
this .DLL in components produce with it.  Many 3rd party .OCX's were
built this way, so you need to ship MSVCRT.DLL with your setup.
(Some machines have it from other sources, which explains why your
setup works on some machines.)

-- Rick
--

(Rick Rutt is a system architect living and working in metropolitan Detroit.)

The problem most likely is, that you also have VB  5 on your system (am I
right??).

This introduced some new system controls, which require minimum version levels
of som DLL's. These are of course available on your system. so everything works
fine here and you will not see any problem, until the first customer with an
"older" system calls in.

The only solution to that is: keep VB 4 and VB 5 separate.
Winfried Kaiser
Fortune Systems GmbH & Co.
Germany