>>
>>You may have a problem with the version of DCOM installed on your system; if the registry entry HKEY_LOCAL_MACHINE\Software|Microsoft\OLE isn't present, you need to take the appropriate steps to install DCOM on your system, as I've outlined in the FAQ here on UT, and as discussed in an MSKB article based on the FAQ entry here.
>
>did all that last week. Or rather, checked it. Already installed
>
>>
>>If you uninstalled VS6 under NT, where you had installed any Service Packs subsequent to the initial VS6 install, you'll probably have to reapply the NT Service Pack, since uninstalling VS6 may have resulted in restoring an older version of a shared component updated by both VS and the Service Pack. I'd advise installing NT SP5 if you can, and if IE5 is installed, make certain that version 5.00.2314.1003 is installed.
>>
>
>yup thats the one I have...
>
>again though, you refer to VS6, I'm a humble vfp only user, is there a possibility that this means I'm missing a possible fix that only comes with vs6 or should I have flushed something else in me de/reinstalls?
>

Not at all - VFP6 is a part of VS6, and if you apply VS SP3 to a system that only has VFP6 installed, you get the same thing whether you installed just VFP6 from the Visual Studio distribution, or the VFP6-only product. There is no separate patch for VFP6-only installs, any more than there were separate updates to VFP5 whether sold by itself or part of the previous VS97. It's the same code base.