Greg,

The VFP compiler is pickier than earlier versions. You can check the PRG's by doing a COMPILE *.prg in the command window. You'll have to do each directory separately, if they are scattered in multiple folders. VFP should stop on all errors in PRG's during the compile.

The PRG's are not the "not a table" problem. Those must be your reports, which are stored as tables.

If a project build fails, it sometimes leaves a trail. Open the PJX as a table (USE myProject.pjx) and BROWSE it. Scroll down the TimeStamp field until you find a record where timestamp is empty. Chances are, that's the file that crashed your build. From your description, I'd expect a corrupted report file.

Of course, back up your project before mucking around in it. That being said, you can BLANK FIELDS TimeStamp ALL to make sure all timestamps are gone before closing up and re-trying the build. If it fails again, repeat the steps to open the project as a table and browse down to the empty timestamp.




>>Greg,
>>Check to see if "it" added any files that you may not have transported. I'd open the .PJX file and check the files at the end to see if any aren't yet in the converted format. (Also make sure none are marked Read-Only - this can cause a lot of trouble for a project build.)
>>
>>Rick
>
>Rick,
>There was a strange file at the very end that had a "t" as the first letter and then the name of the project. It was listed as a program file but showed no code when I tried to edit it. I deleted it, and tried to re-build, and continue to get the "not a table" error. Also, none of the files in the project is marked as "read only".
>
>I might add that this particular app, although it was in FPW, does not contain any screens. The person that originaly wrote it apparently changed all the screens to .prg files. The project only contains .prg's and report files.
>
>Greg