>
>With multiple indexes (or TAGs), each index (or Tag) would have a primary key, right? The primary key is the first "field" in the index key (example CUST+INVOICE, CUST is primary key). The same table, could have a different primary key for each index! Or, it could have the same primary key for a variety of secondary keys (or "sorts").


No. The PI should be a separate tag by itself. There is no need to concatenate the value to other tags. In fact, I'd advise against this. It makes the other tags unnecessarily large and makes SQL SELECTs, SEEKs, etc more complicated.

>
>I'm curious - are most VFP developers using VFPs native DBMS, or - are they going to SQL? Would it be to MS's advantage to drop VFP so that every commercial app we develop (and distribute) requires the enduser to buy a copy SQL 7? Right now MS gets nothing when a VFP native is distributed.

My guess would be that most VFP developers are using native tables.


>
>Terry