>>>>>
>>>>>I meant to write recordsource=''. I tried it a few years ago, it caused all kinds of problems. My method have never failed.
>>>>
>>>>Both methods have pros and cons. Zap could lead to destructive and irreversible results while = "" would only effect display. I only mean it's not an uppercased "NOT" to use thing.
>>>>Cetin
>>>
>>>I have used the zap solution for years, and I have never had any trouble with it so far. I use it with both for small tables, and for large tables, all are DBFs. The largest I use regularly has more than 5 million records and a size of 950MB.
>>
>>Tore,
>>I don't believe you're zapping and then refilling with data those tables. Did you really zap and then append from somewhere else that 950Mb table???
>>Cetin
>
>No, I select from the 950MB into a temp cursor. Then I select a subset from that cursor into the same cursor, in a loop. When the loop is done, I zap the main cursor, and append from teh temp cursor.

Yes Tore,
That is the point I mean. If we simply suggest to use "zap" then a novice might do it on live data! A cursor is used in between anyways and that means you have some code in between. zap+append from only has advantage of keeping the order of columns in synch with the grid controlsources. It's simple and effective, I agree.
The other technique too, can do the control of synching either directly in 'sql' getting the data or via a routine (such as ones that I have in my grid class - they simply save/restore column order/width etc per user's preference).
One or the other, care to some degree should have to be taken.
Cetin