>>>>Hi Larry - I finally got it to work. The trick is to SET DELE OFF. I missed
>>>>that one... thanks.. do you think I should use a VIEW instead of the a LIVE
>>>>TABLE?...thanks again...rob
>>>
>>>
>>>Rob,
>>>
>>>There are a few questions lingering....
>>>1. Why does your app generate so many blank/deleted records?
>>>2. Why don't you want to PACK?
>>>3. Are you using table buffering? If not, this could help answer and solve questions 1 and 2
>>>
>>>Also..
>>>IMHO, Larry's thought was right on the money. You should never SCAN or SKIP through a table looking for a single record. And SET DELE OFF was only the tip of what was wrong with how you're handling this. When this table gets bigger, I'm assuming it will, your performance will get killed. Take a good look at Larry's code and replace as much of your code snippet with his as relevant. Most importantly, make sure you understand WHY his code will out perform yours every time.
>>>
>>>HTH
>>
>>Hi Matt... you are right, Larry's code works and I am using Larry's it...
>>thanks Larry..
>>
>>>>1. Why does your app generate so many blank/deleted records?
>>>>2. Why don't you want to PACK?
>>>>3. Are you using table buffering?
>>
>>I am coding a way the users can edit the COMBO BOX on their FORM. Should I have used a VIEW instead of a GRID? I am using a table and in a network environment and I did not want to PACK. If I use TABLE BUFFERING, then the users will have to SAVE/ABORT. I am tring to make EDITABLE COMBO BOX (a GRID) easy to use. If the users click on the ADD button, then they will get an APPEND BLANK or a RECALL from the deleted record. What do you think? thanks rob
>
>Matt, one more COMBO BOX, eh. Don't tell him about your arrays. It will work OK, but too complicated.

I am interested in Matt's arrays...thanks..rob