Jay,

Another solution to this problem, which might be better, is to use view for Lender table and requery it while navigating on the grid. Do you think, it's better?

Thanks in advance.

>Nadya,
>
> Off the top of my head...
>
> When setting up your data environment (e.g. in Load event), do the following:
>
>

>USE Lender AGAIN ALIAS Lender2 IN 0
>

>
>
>Then, in LendRev.Search()
>

>local lnRecno
>lnRecno=recno('Lender2')
>thisform.DataEnvironment.InitialSelectedAlias="Lender2" && Search form uses this property
>dodefault()
>thisform.DataEnvironment.InitialSelectedAlias="BldMstr" && Restore it back
>

>
>This is the code in AfterRowColChange for BldMstr grid:
>
>

>LPARAMETERS nColIndex
>local lnRecno
>lnRecno=recno('BldMstr')
>with this
>   .parent.GrdHglt1.Highlight_Row()
>   .statusbartext=space(20)+"Record "+ ;
>	transform(m.lnRecno)+ ;
>	" of "+transform(thisform.NumberOfRecords)+' in '+alias()
>endwith
>thisform.navstand.navupdate()
>

>
>This suggestion is simply to "keep it simple." By using 2 separate "views" of Lender -- you can use 1 for searching and the other for viewing without having to set up for one or the other. That should avoid the problem of the table being in the incorrect state for the desired operation.
>
>Jay