>I am starting a project to develop some tools in VFP5 that will utilise tables concurrently used by a FPW2.6a system. Whilst I can access the tables as "free tables", I would like to base the new tools on Views based on the 2.6 tables. The 2.6 tables all have a Codebook 2.6 psuedo-primary key field cID c(9), which has ID's generated by Codebook's NetID() function. Therefore, there is a unique key value in the 2.6 table. Does anyone have any experience with this approach? I have read in the VFP help that views need a "primary key" in the source table to allow accurate/successfull updates. Will the 2.6 cID field value do? Any comments/tips/ideas very much appreciated.

There is no special requirement for the ID field - it just needs to be unique. It is similar to having an index, wanting to update a record and issuing a seek to find it. The view will assume the first record found is the one you want. So, as long as your field is unique, it will do.