Bruce,
This was again one of the cases where I have one smaller update form being called from multiple browse procedures that are placed on a large update form (mimicking queues in list boxes on an update form). The issue was how to identify which browse is calling the small update form, being a called as a popup. A unique ID from the browse would only work for change and delete actions, but not for insert. So I needed something else to indicate which browse is calling insert on the small update form. If the small update form is called as a page, I can add parameters to the URL. But as a popup there are no parameters. It would have been nice for the browse instance to have it's own packet of information that can be used when generating the update form.
I solved the problem by copying the small update form's procedure for each instance of the browse. Each instance will then know what ID it's being called for.
Thanks
Thys