We are using a DB procedure which generates a new ID everytime. We are calling this the moment a user opens up the record in new mode. This is the connecting factor b/w Form A and Form B.

Would like to make these things clear:
* Its out of question to push all fields from Form B to Form A. If this was possible, there would be no need for having a seperate form, we could have as well captured all data in Form A itself.
* We are on 5.1.2. hence Audit feature is not available.

If you use DB capabilities, prefer using a sequence than a procedure. This is most efficient.

But using a self made ID or a GUID to make the relationship, the context is the same.

The solution has been done by Mlevy.

Yes yes dear Vince if we are in release 7 of AR System

GUID is available since version 5 of AR system, but not the Archive process...

I think we are digressing from the topic.

The problem is not in linking Form A and Form B (either using GUID or anything else); the problem is in deleting Form B record if Form A is not saved, without using escalations or Audit (not avlbl in 5.1.2).

Thanks.

Putting this question in another way, is there any way to capture whether the user has clicked on 'Yes' or 'No' in the dialog - 'The changes you've made to XXX form have not been saved. Do you wish to close the window' ??