Keith:

#1 -- Here is my fist, please walk vigourisly into it a number of times. (If you knew it wouldn't work and you were going to get that reply, it would have saved just bunches and bunches of my time if you had mentioned that.) :-)

#2 -- This works (at least, everyone tells me it does, I personally use views whereever I can.) BEFORE CHANGING ANYTHING (note the polite emphasis) set the record source to '', then make your changes to the cursor, then set the record source back! I've had people tell me it doesn't work, only to discover that they are changing the recordsource BEFORE setting it to a blank ('')

>Hehehe, I should have known I would get that answer... We do that, all of the data comes up fine, but the CONTROL TYPES for the fields etc, is reset to the basic type for text, which is a textbox, aswell the previous VALID methods on the field are set to "" / BLANK. Herein is where the problem lies... Data looks wonderfull, it is just the validation and entry formats that get erased...
>
>Try it... create a table (free table), create a grid etc.. set some validation rule on the textbox, then do what you suggest, reset the recordsource to "" then back to the table. VOILA your validation rules will disappear...
>
>THANKS
>Keith
>
>>before refreshing the tables, set recordsource to '' and then reset it back after refreshing.
>>
>>>We have grids that are bound to temporary tables, these tables get refreshed with the standard recordsource="PAYTEMP" for example, unfortunately all of the standard base methodology that was associated with the textbox / combobox within the grid is lost when you reset the grids datasource...
>>>
>>>Is there an easy way around this..
>>>
>>>Please note the temp table is NOT within a database as it is created from an ODBC call to an SQL server etc...
>>>
>>>THANKS
>>>
>>>Keith
>>>
>>>PS: another problem is grid scroll bar bleed through when we have another control overtop of the grid, sometimes the darn up down arrows pop through when scrolling another grid overtop... looks like a FOX error, but who knows...