Use the CLEAR ALL, CLOSE ALL thing and you should be fine then. Somewhere (possibly during the wcstart that brings up the menu) the non-complete libraries are loaded and the Clear all and Close all gets you to the right place to start from.

+++ Rick ---

>Rick,
>
>Here are our findings:
>
>1. If we run the WW Connection server *first* then the WW documentation then the errors occur. If we then run the server *again* with the documentation still running - everything is fine (that we have seen so far).
>2. If we run the documentation *first* then the WW Connection server everything appears to be OK.
>
>Please advise.
>Thank you.
>
>>Alan,
>>
>>Not sure why this should happen. wwResponseFile gets loaded with the core classes and should always be available unless you used SET PROCEDURE somewhere without the ADDITIVE keyword.
>>
>>If that's not it try the following (actually try that anyway):
>>
>>Go to the command prompt and:
>>
>>

>>CLEAR ALL
>>CLOSE ALL
>>RELEASE ALL
>>
>>DO WCDEMOMAIN
>>

>>
>>It's possible that when you ran the demo that the CONSOLE is still loaded. The Console loads some of Web Connection's classes but not all of them and it's possible that this somehow affected the loader.
>>
>>
>>+++ Rick ---
>>
>>
>>>I have 5.0 build 5.22 installed and configured with VFP 9.
>>>I ran the demo server and when navigating around in the documentation to check out the demo controls I am receiving the following error:
>>>Class definition wwresponsefile not found in program wwprocess.prg
>>>The line of code is
>>>*** Now create the Response Object
>>>IF VARTYPE(THIS.oInternalResponse) # "O"
>>> THIS.oInternalResponse=CREATE(lcHTMLClass,lcOutfile)<--