>I am desesparately trying to install the users with the needed dll or whatever to run my crystal report within the application.
>
>I am using Crystal report 7 and my users are running win98. My application is in vfp6 (.exe so I just install vfp6r.dll and vfp6renu.dll and it is working).
>
>I did put Cryst32.ocx and foxpro.int in the WINDOWS\SYSTEM directory but it still tells me that the ocx is not registered?
>

You aren't doing an adequate install of either the VFP6 runtime or the OCX. In spite of your beliefs to the contrary, you need to do significantly more than simply copy two files in place to put the runtime files in working order on a system. If you have religious convictions that prevent you from using a Setup Wizard created runtime install, at least examine the .DEP file that describes the runtime dependencies for the VFP 6 runtime files in the .DEP file in the DISTRIB.SRC directory, and the .REG file that describes some aditional required registry keys to make it work. You can use Setup Wizard to put just the runtime in place, and do everything else you want by hand, but you aren't in DOS any more, Toto...

The same is true for OCXs - they need to have more done than just to copy them in place. The OCX may have runtime dependencies; check the control's documentation (RTFM), or use a tool like the Visual Studio DEPENDS.EXE to check what .DLL entrypoiints and OLE components are needed by the OCX to get it to function.

You have to register any OLE component as well, either programmatically (see Paul Tatavu's entry in the FAQ for details on using the slef-registration entrypoints via DECLARE...DLL) or via the ubiquitous REGSVR32.

If you insist on not doing things properly, your install isn't going to work properly. There really is a reason that people use installation tools capable of managing the install process better than just copying things onto a disk drive, and Microsoft goives you a tool in Setup Wizard capable of doing the runtime install correctly.

Of course, you might know more about what's needed than the rest of us - but those of us who use the Setup Wizard-generated runtime install, or who emulate its behavior carefully to put things in place right, aren't having problems with our install processes...

>Any idea?
>
>Thanks
>Eric.