>Hi all,
>
>In all my years of using VFP I have not encountered this before: is it a bug or have I missed something really important.
>
>a) client has app installed on server as F:\Claims
>
>- config file has a PATH statement into some subdirectories e.g. PATH=REPORTS;FOXFIRE;PHDBASE
>
>b) I was at their office connected on my machine and all my dev stuff is in D:\MCKELLAR
>
>I fired up the client's .exe on their network from my machine as I have done for years and was manually updating some data there. I noticed though that one of the views was not "taking" a value that I had put in. I would open the view, insert the date, close and save it and then it was still blank when I re-opened it. This is a form I have not worked on in some time.
>
>I thought "holy cow", how come the data is not being committed.
>
>I traced it down to the fact that somehow when the view was being opened, the app was "reaching back" to my D: drive and picking up my test table there and so the value was being written out to my local table, not the one on the network.
>
>I had no idea that this could happen. There is nothing in the path statement on the network to allow it to find the file on my D: drive. And anyhow, the table is in the root of the startup directory on the network so it should find that copy first.
>
>Does the .dbc contain a hard-coded path for views that it then uses if it can find it with that path? Users have never had this problem as they don't have any of the data locally. I use the data environment to open the views and I noticed that it contains the full path of the development machine (e.g. "D:\Mckellar\Dbfs") but I thought that this was safely ignored when running on the network.
>
>Albert

Maxframe comes with a utility to remove pathing from not only the DBC, but from the scx and vcx files as well.