>>>>Yes. All you are doing is declaring a DLL function. This is supported under any version of VFP. You will need to have the OCX and all of its support files on the local PC. You can use the VS utility Depends.Exe to determine what files are needed for the OCX to work. You can also get this information from the dependency file. It is usually named the same as the OCX but with DEP extension. It will list the files needed for the OCX to work. For example, Comctl32.OCX needs the following:
>
>Larry,
>
>Sorry for redirecting on old thread - but I figured you would know the answer to this. Does re-running

regsvr32 myocx.ocx

multiple times harm anything? Does it just "replace" the old enty or create another one, causing potential conflicts?
>
>Also - can we leave the OCX in our app's directory or does it need to be down in the system?
>
>TIA!

Since Larry's gone on a cruise (and won't be logging in), I've never seen a problem with re-registering an .OCX. You can have your file anywhere, as long as you register it there using a path. If there's no path given, I'm pretty sure it assumes your system folder as needed.