>>As anyone ever encountered a scenario where a user enters a Company Name in a field on the screen,
>>and when the user presses SAVE the save data is different.
>>
>>Our client claims this happens, though we cannot create the problem.
>>
>>ie..
>>Find Record -- ABC Company from look up database (Companies.dbf)
>>
>>Screen Shows: ABC Company
>>Enter Notes :
>>
>>Clicking save (replace memory to datafile - Newnotes.dbf and ftp)
>>
>>The screen shows ABC Company, but the new record says XYZ Company
>>(which is also a company in the look up file)/.
>I have experienced a simmilar problem with a page frame edit screen. When the user goes forward or back through the database on say page two - the informaition on page one is not updated (ThisForm.Refresh). They make their changes and when they save them the wrong names (text boxes on page one) are saved. I corrected this by modifying the save button to refresh all the pages before saving ( Page1.Refresh, Page2.Refresh ... then save). This obviously is a brute force solution but it worked.

Terry and Glenn,
Glenn, your problem with the PageFrames is a 'feature' < eg > of VFP. What you need to do is put a "This.refresh" in the Activate() method of each page. This will update the controls on each page ONLY when the user tries to view it. This will save a lot of the user's time when saving.

Terry, it sounds to me like you are moving the record pointer at some place in your code, so when the user saves the data goes into the wrong record - or to the EOF() 'empty' record, which may be worse.

Are you using private datasessions? If not, another form may be moving the record pointer. If you are, then check to see if you've moved the record pointer in any fashion. Do you have relations set? They often will move a child record pointer.

HTH
Barbara