Any idea how someone submits a bug report on something like this - surely we don't have to normally refresh an editbox that is bound to a view to be able to query the object's value. I have never submitted something before so have no idea how to get it into the proper channels.

Thanks,
Albert

>Perhaps it's a deja vu and you were the one that found the problem and I used the solution too <g>
>
>>Hi Naomi,
>>
>>Your comments triggered a thought and I remembered that I had to put code into the Activate() method of Page 1 of the pageframe to handle a display problem with the memo fields. Here are my notes from that time:
>>
>>

>>
>>* This code was inserted because for some reason, cannot always get the Opening and Closing comment memo fields to
>>* display correct ie. if the form is fired up, they are okay but then if we go directly to page 2 without editing on
>>* page 1, when we come back to page 1 the memo fields are "greyed out" until we click the cursor into them; this was
>>* the fix suggested by Art Berquist at VMP
>>
>>THIS.edtOpeningComments.Refresh()
>>THIS.edtClosingComments.Refresh()
>>
>>

>>
>>I am going to try inserting a .Refresh() before querying these controls and see if that works. But even if that works, still wierd in my mind.
>>
>>Thanks,
>>
>>Albert
>>
>>>That's a bit weird, but I vaguely remember I had some problems with pageframes and value property of textboxes in VFP6. You may try to search my old threads for this kind of problem, but for now try to do something like
>>>

>>>if type('thisform.pgMyPageFr.Page1.myEditBox.value') = 'C'
>>>  lcValue = thisform.pgMyPageFr.Page1.myEditBox.value && full path
>>>  ...
>>>endif

>>>
>>>This will help to track the problem.
>>>