Hi Michel,
I just had a very similar problem with a new install (well an old project I'm moving to VFP8). The answer was to delete *.fxp from the wconnect\classes folder, and then do a compile ....\wconnect\classes\*.prg.
All was once again well with the world.
Make sure that the wconnect folder is in the path so wconnect.h can be found.
Cheers,
Andrew
>>Looks like you need to recompile the wwc base classes and make sure wconnect.h is in the path. I'd delete all the fxp files in the wconnect/classes folder first.
>
>If I recall correctly, when it goes up to that point, where Visual FoxPro is loading, it's to load the basic WWC demo. So, it seems the installation went ok. I am able to go in the admin panel and will try to setup a small project to test it.
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
