>OK, I've done that and it works great. Thanks!!!

Glad to help.

>Now let's say they hit the new button for the child record with out hitting the save button first.

First, I would now allow the new button to be enabled whilst there are un-saved changes, unless of course, we were dealing with table buffered data (which you don't want to from your earlier comments). I wont explain how to do this unless you want to do it this way. Let me know on this point.

>Does it automatically do a save?

Not tried this but if you are row buffered, moving the pointer automatically forces an update. So, if you hit the new button, by default, the pointer will move from the current record to the new record so, I would have to say that it will likely save the current record when you hit the new button for a new record in the same cursor.

>Codemine still says that I have to save the Day record before adding any more Group records.

Look at the form's "lConfirmSave" property. If this is set to NULL, then the Save message that you are seeing is determined by the value in the "%Local.Data Entry.Confirm Save On Navigate" key in the Codemine application registry. If you change this key value or, set the form's "lConfirmSave" property to .F., you will not get this message. The reason this is driven by a key in the Appreg02 file is so that the user has a choice. Some users want to be prompted to save a record, others may not be.

HTH