Of course you are correct. The temp files are all on the workstation side and on further testing I find they are going exactly where they are told to go. There is no server or network issue. If I run the app locally on one box one XP box works, the other doesn't. As far as I can tell they are set up exactly the same way. If I use a config file to direct the tmpfiles to c:\temp they go there, if I don't they go to the users temp folder. On Box A the app works, on B it fails on the line with attempts to index the view, saying it cannot modify the file.

I have checked every folder/user permission I can find. They appear to be identical and wide open. Logged on as administrator on both boxes.

On box B - the bad box - I can open the view in developer vfp and index it, directing tmpfiles to the same place the app is directing them. I can also write a test app prg, compile it into an EXE and that exe can index the a view. So - the only difference is that VFE uses macro expansion to create a command that indexes the view. I am going to modify my test app to see if that makes a difference.

But in any case - one box works - one doesn't and I can't see the difference between them. Both XP SP1, no firewall, full permissions on the folders, logged in as admin ...

It is not just one bad box. All my machines run the app fine. Client - about half can, half can't.

Cok Tuhaf

Tebrik ederim on your anniversary.


>The view's tmp file and its index are both created in the temp folder. There shouldn't be any tempfiles on the server (or if there would be folder on server needs readwrite access).
>To OS either from within app or explorer it's the same logged on person. If you're calling a COM object, its security settings might be different.
>
>Well I wish I could go to Deniz tonight too :) Maybe on our wedding anniversary next week.
>Cetin