Sagol, Cetin Kardesim

Iyiim. Fakat beyinim corba gibi

I have tmpfiles=c:\temp on the workstations config file. But I believe when a view is created and indexed there are actually two tmp files created, one in the folder with the data, being a tempfile of the view itself, the other in the tmpfiles folder, related to the index. My understanding is that when the view is indexed, the reference to the index must be written to the header of the tempfile on the server.

I think this has something to do with managed code vs unmanaged code. Since VFP and its dbfs are not a "service" the OS does not know who they are for purposes of allowing creating and modifying files. If I do it from Explorer on the workstation, I can do it because the user had permission, but if the app tries to do it, there is no permission. Does that make any sense? ( I am not sure why, if that is the case, the tempfile for the view would be able to add and change records, which it obviously can, but I have been told the problem is in writing to the header )


I am going to go on-site Monday, put my laptop on their network and see if I can open and index a view in developer VFP.

I thought this might be a very common problem and I would receive a hundred answers from other who had faced this. My ignorance of security issues and permissions on networks is so great that it never surprises me when I find I don't know something that everyone else in the world knows < s >

Kalbim daha Izmirde. Keske bu aksam Deniz locantasinda olsaydim ...

>>
>>TIA
>
>Charles.
>How are you or Nasilsin :)
>Serverside tmp file ? Why create view's tmp files there. tmp files are expected to be at local for performance. tmp files might not be created if the 'temp' folder is readonly or hidden\system (same if user doesn't have needed rights to folder). Other than that view indexing would fail if it's attempted to be created after its buffering is changed to one table buffering.
>At your local setup I think it works because you have all the access rights to folders.
>Cetin