Bret,

Take a look at the MSDN KB. I seem to recall something about SET SKIP problems, but I don't have my TechNet with me and this laptop sucks trying to keep 2 IE sessions going...


>>Hmmmm....I still don't see why you couldn't use a view and the ORDER BY clause to put it in the order you want it and make it parameterized on document number. As to the original question, check your Column data settings and make sure that the controlsource is correct for each and that the Bound property is set true. Could be some weird foul-up between the Column settings and control settings.
>>
>>
>>>This particular grid is used in a pick a record type form. The locate button is pressed on the main form and then this grid will come up and allow the user to type in a document number. As they type then the grid positions them at the record. It is very slick and the user like to be able to see the document and revision history as they search throught this grid.
>>>
>>>So a view would not do as I would have to create this view and have it ready (indexed) everytime this screen comes up. The root table is 35,000 records and the master tables has 80,000 revisions/changes.
>>>
>>>Unless I am missing something.
>
>I talked this over with our users and they like the ability to instantly jump to the record as they type. The grid is sort of like a what jkey was in FoxPro 2.6. If I type and A the grid positions them on the document numbers that start with A and as they type the record is found. That is what the grid can do, but a parameterized view would mean that they would have to enter a document number then ask if it is there (requery). I could use a non parameterized view that is made up of the 4 fields (80,000 records) indexed on document number, but that would take too long.
>
>I will look at the column data settings and such. I appreciate your time.