>I do not have VFP3 installed either, just VFP6 and 7. No OCX should be dependent on anything except the presence of a 32-bit OS.
>

That's not strictly true; OCX files, representing ActiveX controls, are often dependent on operating system components related to COM services (eg the OLEAUT family of DLLs, DCOM services and the like) as well as the base DLLs providing common system routines that the OCX calls on. These file dependencies are usually documented by the vendor, or can be discovered by tools such as the MS Dependency Walker that accompanies Visual Studio.

>>I *think* this is because I've never installed VFP3 on my machine. I think this thing is looking for the VFP3 dll. Is this possible?
>>

It's exceeding unlikely - the OCXes that accompanied VFP3 were not dependent on things in the VFP3 runtime, but on common operating system components in wide use when VFP3 shipped. It's likely that many of these have been superceded or replaced, and in some cases, the provider may have changed since the time VFP3 shipped.

>>I did the path thing and still no luck.