Hi Jet,
I would put a debug break point in the program after doing the insert or edit, browse and check the value of the date field in the view, single step the program up to the tableupdate(), browse the remote view to check the value of the date field in question to be sure that it is filled with a proper date and not blank before and after the tableupdate. Step past the tableupdate() and requery the remote view and check the updated date value. If your remote view started with a valid date before tableupdate, and the requeried view has 12/30/1899, I'm not sure why this would happen.

I suspect that there is either a problem in the control source not set up correcty and not really filling the date field, or for some place before tableupdate the program is blanking the date field. In every case where I have seen 12/30/1899, it has been in a date (or datetime) field in a VFP table updated through ODBC where the date was blank in the remote view when updated to the underlying table.

HTH
Elmer