Steve,

If the Contacts form is in the same application, you could use @FormNewRecord(), but it only adds a new record if the Contacts form is open at the time. That can be taken care of with programming, with the use of @SelectTreeItem() to open the Contacts form in add mode.

Or if the Contact form is in a different application, you could use a technique that I have been using in Q&A for years. I keep some records in my target database that simply have "FREE" in the key value field. First, I XPOST to one of the "FREE" records, overwriting the "FREE" value with a new unique key value. Then I can XPOST to all the other fields using the new unique key value. When the XPOST fails to find a "FREE" record, the programming launches an additional Q&A session with an auto-run macro via @shell, which then adds more records and types FREE into the key value field.

Quote:

You don't have to goto (or even see) the Contacts form; it just needs to be open somewhere within Sesame. If Contacts is a subform of Invoice, that qualifies as being "open". So, you should be able to use @FormNewRecord().

I just realized what you meant by 'goto'. If you use @SelectTreeItem() to open Contacts, it will display the Contacts form. You can solve this by having a second  @SelectTreeItem() to get back to the Invoice form. Something like this should work:

var success as Int

success = @SelectTreeItem("AppName!Forms!Search/Update!Contacts DB!Contacts Form")
success = @SelectTreeItem("AppName!Forms!Search/Update!Invoice DB!Invoice Form") 

I just tested it. It works good.

Carl,

Thanks again for your help. I was able to use your technique to copy the contact info from the invoice form to the contacts form easily enough. I just I could do the same thing without having the form open in the background.

Maybe in a future version of sesame.

For now, we'll get by.

Thanks!

Steve