A few things to try:

1. In the References Dialog of the VB Project, did you set a reference to the VFP DLL?

2. Have you tried to instance the VFP class in an Office app like Excel?

Also, when did you install NT SP 4??


>Hi all -
>
>I am struggling to avoid reinstalling NT and 3 Gb of apps. Is it possible? Here's the situation.
>
>I have a VB dll that uses Createobject to get a reference to a VFP 6.0 dll. For months this has been working fine. Suddenly (with a fresh boot one morning) the VB line (e.g. Set x = Creatobject("FPW.y")) is generating the VB runtime error 429 ("ActiveX component can't create object or return reference to this object").
>
>This problem only occurs on this machine. In other words the same VB dll and VFP dll and tlb will work fine on a different machine. (Visual Studio 6.0, SP2, are installed on both machines from the same MSDN installation disks -- (don't worry, MS, both are licensed under the company's Select program). And if the VFP dll was built on a different machine it still fails on the problem machine.
>
>ole32.dll (v 4.0.1381.117) and oleaut32.dll (v 2.40.4268.1) are the same version on both machines.
>
>VB can run Createobject("word.document") succesfully on the problem machine.
>
>VFP can run a simple dll with, say, Createobject("vfp.y") on the problem. When VB tries to run this same command on the problem machine I get the error 429.
>
>I have uninstalled and reinstalled VB and the SP2.
>
>Both the VB and VFP dlls have been unregistered, rebuilt and registered in any combination we can think of. We have searched the register for the file name (w/o extension) for both an manually deleted anything found, then rebuilt.
>
>We have checked the KB, but not found anything that fits the problem.
>
>The OS is NT 4.0 with SP4.
>
>Any suggestions?
>
>TIA