We are converting a 2.6 app to VFP 6.0 and I've noticed a change in how FoxPro handles included tables. In 2.6, if you included a table in a project file, once the table was opened, it could be included in any select statement. However, this ceased being the case in VFP. Now, the select statement seems to need the original file, even though it is open, browseable, etc.

Anybody have any idea what's happening here or how to work around the problem?

(NOTE: amended post of previous message posted last week in "troubleshooting" category: thread#444441 . Anybody more familiar with porting apps from 2.6 to VFP have any ideas around this problem?)

If you want to reproduce the problem, here are the steps:

steps to recreate:

create table testtable (testfield c(5))
insert into testtable values ('a123')
insert into testtable values ('b123')
insert into testtable values ('c123')
insert into testtable values ('d123')
insert into testtable values ('e123')

create proj testproj

* add testtable as free table and mark as included
* add following procedure and mark as main

Procedure testprog
close all
use testtable

create proj testproj2

* add following procedure and mark as main

procedure testprog2
do testproj.app
brow nowait
select * from testtable

*build both projects as application (app)
*delete or move the file testtable.dbf (it's now part of the app)

Try to run testproj2.app. The table will open. You can browse it, it appears in the view, you can scan it, BUT you can't execute a SELECT statement against it. It generates the error message: "File 'testtable.dbf' does not exist". It does exist! You are currently browsing it...