>Thanks. Please keep me apprised of what happens.

Craig, here's the resolution:

Crystal Decisions Tech Support provided the following:

I have just talked with one of the guys here who has dealt with this problem
(or, at least, very similar) a couple of times before. He has started on a
Knowledge Base article, but has not cleaned it up for publication yet.
Hopefully, it will help you, even in its present state. It sure would help
us to know which (orphan?) components you remove.

Here it is:

Problem:
------------------------------
Customer has created their application and is using v.92 RDC with their VB
app (could be any language). Using an installer (InstallShield or Wise) they
create their deployment using our merge modules and all the merge modules
that they require to run their applicaiton successfully.

Their installer will run fine and receive no errors when installed under an
admin account on a production PC. The program will even work fine under the
account the app was installed on. BUT when you go to run the program under
any other ID on NT or 2K (this does not effect Win 9x) the Installation
Repair will launch as if a component is missing from the installation.

This repair will ONLY happen when you try to view, print, or export a
report. The problem is NOT with Crystal or any of our merge modules.

Solution:
------------------------------
The problem lies in the list of components in the installation package. Have
the customer look through the list of their components and find any
component that is NOT installing any files. If there is a component that
does not install a file they will run into this problem. Since this is a
component that does not install a file then it isn't needed in the
installation package.


In addition, InstallShield provided me with a tool called MSISPY.EXE that can be run on a system to evaluate all installs. It reported that in my application install there was a "Not Installed" status on an empty folder that I was installing under [INSTALLDIR] for future use to hold MS Word documents. When I removed that empty directory and rebuilt the install package, the problem went away. What is still unexplained is that I also have another empty directory (for backup purposes) installed as a subdirectroy under my [DATABASEDIR]. That one is still there and apparently causes no problem. Go figure.

If anyone wants the MSISpy.exe utility, email me and I'll send it or post it to the files section here.