Hi Bret,

I haven't seen that particular behavior before, but why not create a view to populate the grid?

SELECT Root.DocNumber, Master.Revision, Changes.ChangeDescription, Master.ChangeLevel FROM root INNER JOIN master ON rootkey INNER JOIN changes ON changekey


>I have the following tables set up to display in a grid:
>
>select 0
>use root
>set order to tag docnumber
>Select 0
>Use master
>Set order to tag rootkey
>Select 0
>Use changes
>SET ORDER TO TAG changekey
>Select master
>SET RELATION TO changeky INTO changes ADDITIVE
>Select root
>SET RELATION TO root.rootkey INTO master ADDITIVE
>SET SKIP TO master
>LOCATE
>SELECT master
>
>The grid will display 4 fields:
>
>Root.DocNumber, Master.Revision, Changes.ChangeDescription, Master.ChangeLevel
>
>Root is the parent to one to many Masters and each master has a one to one relationship that shows what type of change that is happening to the revision.
>
>When the grid comes up about 70 percent of the time it displays data OK with asterisks coming up whenever the Root.DocNumber is repeated. That is OK as it is easy on the eyes and searches are done on the Root Document number. But the other 30 percent of the time the grid will start to put asterisks in where the revision is and also in the change level field. The asterisk show up sometimes when the revision repeats or the change level repeats. If I close the grid selection form and go back to the screen that called it, then execute it again sometimes the grid is back to normal, other times it is the same.
>
>Is this a bug, has anyone seen this before? Any help would be appreciated.