>This is an ugly fix, but you could use SET PATH to include the target directory of the table in the VFP path. The problem is that the view is basically issuing USE (TABLENAME), so TABLENAME needs to be accessible.
>
>Probably not exactly what you are looking for.
>
>Eric Shaneson
>Cutting Edge Consulting
>
>>Has anyone else noticed this behavior in VFP 5?
>>If you create a local view, either programatically with create sql view or with the view designer, which is intended to send updates to a free table, the view loses it's association to the free table it is intended to update unless that free table is in the current directory or in the same directory as the dbc that holds the view.

If you're using the view designer than the SET PATH is the only way around this. But if you're using CREATE SQL VEIW than simply preface the free table's name with the drive & path where it's located.