Thanks for all of your help. I have learnt a few things about WC to put in the vault.
I don't have a virus scanning of LAN traffic turned on. I also aren't using browsers as the client for this app - the clients are VFP apps polling the server for data. This means that it isn't a browser cache problem, unless I am missing something. I havew noticed if I look in the cache of the browser on a client machine that the urls being hit by the VFP app are in there - ie. I see
http://whatever/myproc.myscript etc.
Have a good sleep - it's already 2:30 in the afternoon the next day where I am.
>Jamie,
>
>>Running 3 instances. I will try just 1 instance after I see if Lauren's advice has done anything.
>
>If the problem is not consistent, but just happens in some situations, but you are running multiple instances in file mode, and especially if the traffic on this web app is heavy, you might have a problem with mixups in the temporary files that file-mode WC creates on each request.
>
>Assuming that you try with just one instance and the problem goes away...
>
>Is the temp\wc directory or whatever you set for the WC temp files located on the same server as web server and the WC EXE? If not, do you by any chance have Virus scanning of LAN traffic turned on?
>
>Is the temp\wc directory (or whatever) being actively scanned by Virus Scanner? If so, disallow that on that directory.
>
>I have seen both of the above situations on a heavy traffic file-mode site cause the temp files to get confused, causing either timeouts or inconsistent results.
>
>WHen you said before that you isolated the problem to a query that later produced the correct info, do you mean that you actually interrupted the WC app when a query produced no records? If not, is it possible that you just have an internet browser cache settings problem that is not requerying the web page, but reads from cache instead?
>
>That's all I can think of right now. I'm going to bed.
Cheers,
Jamie