Hi Walter,

From my point of view you have covered the bases nicely. I do think the extra detail in your response may be relevant to a "final" WISH submission. I also suspect that others will chime in with ideas or worries that will be relevant for inclusion too,

Good luck on this one. I think it would be a HUGE step forward if this one was adopted PROMPTLY.

Cheers,

Jim N

>Jim,
>
>>Yes, I feel that this is an excellent way to overcome a perennial problem in the xBase/VFP implementation.
>
>Thanks, to you for your wonderfull idea !!
>
>>I presume that you would still have a PACK run/do exactly what it does today regardless of the "TableView" in effect. Personally, I would see no reason to do otherwise.
>
>Yes, it does. But if this tableview mode is set to 3, you won't need a pack as much as you do now !
>
>>It sounds like you would like this to be 'variable' from USE to USE or from app. to app.
>
>Well since it is a Table prperty it's variable from table to table. IOW it's NOT a cursor nor dataenvironment setting; it only can be set within the table designer or a DBSETPROP() function. Changing this property can only be done in exclusive mode, because indexes (might) need a rebuild when changing from or to normal mode (mode 1).
>
>>I throw in for your consideration a "permanent" choice instead, on the basis that system debugging could be made much more difficult if some apps. employ your mode 1 while another uses mode 2 and yet another uses mode 3. And I could surely see some trying even to change these within an single app., if only to try to 'improve' performance or even just to see what happens.
>
>Of course, you've got to design your tables well. But if you do, IMO, you won't run into many problems.
>
>Walter,