Mohammed,

I don't catch it.

All I see is that I like to replace warl in mstr. And somehow you mash up selects, grids and replaces.

Keep the replace of the data away from the display of the grid.

Data doesn't deal with grids etc, they deal with cursors,records, vars and sometimes properties.

Grids are interfaces to the user.

Rethink your design and try to write your problem the long way.


Agnes
>hi,
>mycur.wark&&from mstr.dbf ,
>
>append for payroll.dbf with all fields
>
>replace for mstr.dbf just field wark.
>
>
>

>SELECT TAlias1.employeeid,TAlias2.nam,TAlias2.nam4,TAlias1.workdays,TAlias1.absencewp,TAlias1.absencew,TAlias1.uovertimeh,TAlias1.whovertime,TAlias1.vacations,TAlias1.sickvacati,TAlias2.wark  ;
> FROM payroll TAlias1, mstr TAlias2 ;
> WHERE  TAlias1.employeeid = TAlias2.no ;
>  ORDER BY employeeid ;
>   INTO cursor  mycur readwrite
>
>      thisform.Grid1.RecordSource=" mycur"
>         thisform.Grid1.refresh()
><\pre>
>
>thanks
>
>>Hi you,
>>
>>#1 mycur is not influenced by SCAN since payroll is current work area
>>#2 REPLACE FOR will move the record pointer of payroll to EOF. This meeans the SCAN will run once only.
>>
>>
>>Agnes
>>>hi all,
>>>any help to active this code
>>>
>>>

>>>select payroll
>>>zap
>>>append from dbf('mycur')&& ok
>>>
>>>******************************
>>>***no errors no result
>>>SCAN
>>>   M.EMP=mycur.employeeid
>>>   M.MARK1=mycur.WARK
>>>   replace MSTR.wark WITH M.MARK1 FOR MSTR.NO =M.EMP
>>>ENDSCAN
>>><\pre>
>>>thanks

Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off
There is no place like [::1]