>Hi all
>
>I try to use the dll an ocx on the server !
>
>This is my situation !
>I have made a application and copy all the files on the server .exe ,dbf, ocx and dll's
>
>Is it possible to create a short cut from other Pc to this app and dont register all the dll and ocx on each pc. I mean i want my app use the dll and ocx within the same directory. I have always belived it was possible.
>
>I'm probably lazy but register all the dll and ocx on 80 Pc dont turn me on .

Well, in order to work, you need to register COM components (including ActiveX components) so that references to their GUID or ProgID can be handled. And in order to not be either network bandwidth bounded or subject to the vagaries of drive mappings, the OCX and supporting DLLs which require registration should be on the local machine so that someone mapping a drive differently doesn't shatter their functionality; non-registered DLLs (those whose entrypoints are resolved through the C or C++ DLL resolution methods) can be anywhere on the Windows search path, including in the current directory, but again, you're better off putting them on local resources.

Doug Hennig created a class to handle the proper deployment and registration of components to local systems, which can be accessed from his website, www.stonefield.com - assuming that all other things are resolvable without registration, his class is capable of properly registering an OCX at runtime, to make life easier.

Blind copy installs simply don't work right; you can choose to believe me or not. With all versions of VFP coming with at least some tool capable of performing local installation and registration of components, whether through Setup Wizard, VSI or ISX LE, they means to do things correctly don't cost anything but the time to learn to use them properly. And in return, most of the failures associated with improper installation are fixed, and can be supported by other people, including MS Tech Support and people here on UT.

Your decision. Feel free to hurt yourself.