Hi there John,

It's probably not that becuase the save button is on the form. However, it's not on the page but that doesn't seem to matter becuase the other edit box is on the same page and it works fine.

What I did find out through going to the command window and trying to do a replace manually is that the replace works fine in my view but when I go to close the table I get an ODBC error talking about a syntax error in the update command in Access.

I also noticed while investigating that because the field was 255 char in Access, the view I created in FP seemed to see it as a memo field. So I figured that might be a problem. So I shortened the field to 25 char (the other one, the one that's working right, is 80 char). But I'm still getting the same error.

I appreciate whatever help anyone can give me on this problem. If no one can help me figure this out (and if you guys can't get it, I KNOW it's beyond me) then maybe someone could loan me a sledgehammer for a little while? :)

>Hi Denise ---
>
>What is the physical location of your "save" button? If it is not on the form itself, then you're running into the infamous no lostfocus problem where a controlsource is not being updated by the value when clicking on a save button.
>
>
>>I've got two edit boxes on this form. The form was made with a wizard and I think both of these edit boxes were made with the form (as opposed to the combo boxes on the form which I had to add later). Both of them are tied to fields in a view which is based on a remote table (Access, if that matters). One of them works perfectly. I click "edit", put in data and it goes into the table and everything's beautiful. With the other one, I click edit and change the data in the edit box and when I click "save" it goes back to the data it had there before. Changes not "taking".
>>
>>I got so fed up with looking at the properties of the misbehaving editbox that I deleted it and copied the other one to that spot on the form. I changed the control source from viewencumb.rush_reason to viewencumb.desc and changed the name of the editbox but left everything else the same. I figured since this one worked, I'd just make these couple of changes and everything would be fine. No luck.... it's still not updating my table.
>>
>>I checked the view and they both have the checkmark in the update column (I guess that's the one with the little pencil above it) and the view itself has "send sql updates" checked. I checked the Access table and can see no difference between the two fields.
>>
>>I'm completely lost. Could someone please help me with some idea of what else to look for? I would certainly appreciate it.