>This is driving me crazy! Below is a sample query that runs in less than 1 second on my production machine (P133 24 meg ram), but when I execute the same query from one of my users machines (P266 32 meg) it takes 10 minutes. The data is on a NTServer 4.0 and my production machine, as well as all of my users machines are using the same data from the server. The users machines execute the exe from their local drives and access the file server data, just as I do on my production machine. the example query below is a simple join of four tables (all indexed). I also have a notebook as a backup production machine and it also executes the query in less than 1 second. The only difference that I can come up with so far is that the production machines have VFP installed while the users machines are just running the exe. Does anyone have any ideas for me on this? I've run out of ideas and I don't understand why this is happening. I am using VFP 5.0a
>
>*!* EXAMPLE QUERY
>
>SELECT pcdsdata.* ;
> FROM pcdsdata,pcevents,repleads,contact1 ;
> WHERE pcdsdata.parcel = pcevents.parcel ;
> AND pcdsdata.parcel = repleads.parcel ;
> AND pcdsdata.parcel = contact1.company ;
> AND pcevents.repout = 'Y' ;
> AND pcdsdata.stname = "APACHE" ;
> INTO CURSOR queryrepleads ;
> ORDER BY pcdsdata.stname,pcdsdata.stnumb

Some ideas:

1. Are both machines working with the same code page? (I believe that when code pages differ, VFP has to do extra conversion work.)

2. Do users store their TMP files on their local drives? (Having to create TMP files on the net is a sure "slower-up".)

3. Does everyone access/use the same CONFIG.VFP file?