Thanks for replying Steve. I was double-checking my code (since it worked fine yesterday)and found out what I changed to cause it to start failing. The grid was actually updating as it should, it is just that one of the columns gets its value from bouncing the value in the table against a procedure to change its display value. It was my own silly mistake! I was running the routine outside of the project for testing purposes and modified my code to change the display value in the grid in a separate procedure based on the actual value. The grid itself does this, so it when I ran my new code (without removing the manual call to the display procedure) it was bombing. All is well again and it is refreshing as it should.
Tracy

>Tracy,
>
>I would suggest that you set the grid's recordsource to the empty string before you do the processing, and then set it back after the processing is complete.
>
>>I have a program that contains several procedures. The main portion of this program opens a table whose name is contained in the variable 'tablename' because it may be one of several different tables with the same structure. Following that it calls a form which contains a grid whose recordsource is (tablename). When the form opens up, it contains all of the records from the table as it should. When I choose an option on the menu which pulls in data from the com port and inserts it into the table (tablename), the table contains all of the records as it should, but the changes to the records are NOT reflected in the grid. I've verified that form's datasession is default. I've included a comform.refresh (and tried comform.grid1.refresh also) after the table is updated and still the grid does not refresh. I can browse the table and see the updated records are there, but they are not in the grid. The strange thing is that the grid used to be updated as it should be. What am I
>>overlooking? Is there another way to get the grid to requery the table?
>>TIA,
>>Tracy