No, the replace command works in current workarea and when you don't specify a scope on the current record only.
Take a look on the controlsource of the txtsaved textbox. Something else is causing the pic to change, not this replace. Not, if it's right after the append blank.
To make sure, don't do a series of replaces, don't append blank, instead do one insert:
Code:
INSERT INTO yourtable (Id_no,lname,fname,mname,major,yr,pic) VALUES (thisform.txtId_no.Value,...)
All your controls then should be unbound, but you'll only be able to enter new records then, not modify existing records.
If you bind controls to the table, they will always modify the current record, also a new one you add with APPEND BLANK. Then you don't do any REPLACE, you simply enter the data while being positioned on the new record. The controlsources are a two-way connection to the data, displaying current data and modifying it interactively. There is no need for code putting the values into the table fields then, the controlsources do that.
There are a lot more things to say, eg IDs should rather be autogenrated and won't ever come from a textbox, eg using data binding (controlsource) you'd not need these REPLACES at all, because controlsources set the field values, and much more. It is quite obvious despite your choice of name "keepfoxing" you are not a frequent fox developer and may have just started using FoxPro. I suggest you look out for some basic tutorials, especially about database theory, that also will be helpful, if you later switch to something else, DB and SQL knowledge helps you find other jobs with data centric business applications.
Bye, Olaf.