>> the approach of having a second update form on the update form for the point record, is that a good approach?
no.
A better approach, one that will work, is to call the form you want to call. In the example you sent me that would be UpdateUser, in your real app I expect it's UpdateJob, or whatever.
So now the issue is getting the correct record loaded in that table. I'll refer to the example you sent - the map is plotting the accidents, but you want to UpdateUser. So in UpdateUser, in the InitForm routine you need to prime the GUID value of the user to edit.
At this point all you have is the sesison value for the Accident. So the code goes something like this;
Access:Accident.Open()
Access:Accident.UseFile()
Acc:Guid = p_web.GSV('Acc:Guid')
Access:Accident.TryFetch(Acc:GuidKey)
User:Guid = Acc:UserGUID
Access:Accident.Close()
p_web.SetValue('Use:Guid',Use:Guid)
p_web.SetSessionValue('Use:Guid',Use:Guid)
This loads the Use:Guid into the Value, and SessionValue queues, and from there the form can take over.
Cheers
Bruce