Cetin, I think I have got to the bottom of it
I did have a filter on the file (set filter to cusref = thisform.objMemvar.Cusref) which is set in the calling screen.

In the called screen,presumably this filter is still on but it cannot find ThisForm.. now because the ThisForm is now the calling Parent.

(Maybe the reason it did not error out on a Seek 'abc' was because the seek got an EOF and it did not trigger the filter ??

Anyway, this poses another problem. Is there a way of maintaining a filter across called screens (I have set up called screens so they share the DE)

regards,

Gerard





>Yes strange,
>Reading 'a seek on the MyVal, but it still comes up with an Unknown Member ObjMemvar on the Seek Line, even though at this stage the Seek is looking at a completelely different variable' I thought in any case you were getting the error.
>Cetin
>
>>Cetin,
>>
>>I also just tried a Seek 'ABC' and this works fine
>>
>>So:-
>>
>>Wait window ThisForm.oCallingObject.ObjMemVar.Cusref --> is ok
>>Seek 'ABC' --> is ok
>>Seek ThisForm.oCallingObject.ObjMemVar.Cusref gives an error
>>
>>..strange behaviour ?
>>
>>Regards,
>>Gerard
>>
>>
>>
>>
>>
>>>>Hi.
>>>>I have a form, ehich is being called from another form
>>>>On the Called Form, a command button has following code:
>>>>Sele SDA
>>>>Seek ThisForm.oCallingObject.ObjMemVar.Cusref &&(Seeks a Customer No.)
>>>>
>>>>This gives an error: Unknown member OBJMEMVAR. just first time it is used. If I ignore the error, when it goes into the same code a second time, its fine.
>>>>
>>>>I'v also put a Wait Window commnad before the seek, and I can see the data in ThisForm.oCallinhObject.Cusref fine
>>>>
>>>>In the debugger, ThisForm.oCallinhObject.Cusref shows the correct data also.
>>>>
>>>>
>>>>I dont understand how . both the wait window and debugger is showing the data ok, but it still comes up with the error. I've also tried doing a MyVal = ThisForm.oCallinhObject.Cusref (which workds fine) and then doing a seek on the MyVal, but it still comes up with an Unknown Member ObjMemvar on the Seek Line, even though at this stage the Seek is looking at a completelely different variable .
>>>>
>>>>Anybody got any ideas on how this is happening.
>>>>
>>>>Regards,
>>>>
>>>>Gerard
>>>
>>>Gerard,
>>>Sounds like you're seeking < g > the error in seek but actual place is elsewhere. It might be anything that would need a reevaluation as pointer moves (ie: a filter expression). To check if that's really the case do a seek with known value written literally (actually you did this already with myVal).
>>>Cetin