What my long lost cousin Blake says is true. (no we're not related, at least I don't think we are... :P )
Alternative:
If the User is going to Save & Keep Working, open the new record in a new tab or window. When the User is done with the record, close the tab or window and return to the previous (parent) page.
Downside, the User must refresh the page to see child record changes but you don't have to try to hide the Save Button using magic.
This is right at the edge of Quickbase - Custom Pages wilderness. In JavaScript you can use the window.location function and parameterize the parent rid. Check Mozilla MDN, HASH and strip. Write a page in the Code pages area, then you don't have to "hide" the Save button.
Jim
------------------------------
Jim Harrison
------------------------------
