If you read the code from that .js page, it might actually be a good thing that it doesn't work. That code page calls a series of '.click' commands, one of which is the 'save and keep working'. If '.click' commands could be initiated by an 'onload' command, then your browser would go into an endless loop of saving and saving and saving every time you load a record.
You may not be able to get around the need for creating a button in each of the child tables to push the user to the next stage of the parent record.
------------------------------
Brad Lemke
------------------------------