>>I have had a problem before with servers when they try to create the foxuser.dbf file. If you are able to debug this, you would find that it gives the message "Convert foxuser to latest version?" or something like that. Anyway what I did was put a valid foxuser file in the NT system32 directory and that fixed the problem.
>
>
>Hmmm... if this is really the problem, wouldn't set resource off in the config or the setup program be the way to go?
>
>BOb

Yeah, that's what I am doing now, but I just remember the hours of fun I had tracking down the problem. When I ran the server (exe) from an explorer window, it worked just fine. But when I started it up from the browser (having the win-cgi dll start the exe) it ran as a system process and because it was run by the browser, it started differently. I thought it was a permission problem, access rights thing etc, but no, it ended up being a problem with the foxuser file. Ouch!

It's great being able to stop and start the exe with the browser because I can then use FTP to upload a new exe, stop the current one, copy over the new one to the run directory and start it again all within the browser.