You should be able to XPost to another database while it is closed in the same application, but I am not sure what will happen if going to a database in a different application that is closed.

Sometimes the best way to answer questions like this is to try it if you think you can reverse what might happen.  A situation like this should be reversible, try it and see what happens.  Let us know the results.

Quote:

Steve,

I'm not sure about creating a new record in a closed DB. But, I needed to do something similar with Q&A.

The way I worked around it was to use a macro to create many records at once with the text "FREE" in the key field. Then I would simply xpost using the key value of "FREE" to find one of those available records, replacing "FREE" in the target record with a new key value from the source record. You then have a record with you can xpost the rest of the data to.

If there were no "FREE" records found to post to, that's when the macro kicked in to create some.

Carl,

Your creative solution would probably work for me, but I was hoping for something that would require less work.

Bob,

Your idea is exactly what I was hoping to find. I'll try it out and report back as to the results. By the way, how would one know about this option. Is this documented in the manual and I overlooked it?

Thanks for everyone's assistance.

Steve

Quote:

Wrong this time Carl ??? Very unusual.....

See @FormNewRecord(form) on page 173, Programming Guide.

Using @Application would be for a form in the same open application.  To do this in a closed application we would need to do something like @FormNewRecord("C:\Sesame\Data\Application.db!DatabaseName!FormName")

It may be possible to create a record in a closed database.  I know you can add records to closed Access databases and you can modify cells in Excel using DDE technology.

Other programs can be modified using SQL commands on closed databases, so maybe we can do this in Sesame also.  I may be able to try this out next weekend.

Sesame has the ability to record exiting File->Exit as part of a macro. That allows you to record a macro that creates the new record, tags a field, and then exits the program. You can then invoke Sesame from an @Shell command or @ASynchShell (if you have the association set up):

sesame -macro MacroName.mac ApplicationName.db

That will open the app in Sesame, create the new record, and then exit Sesame. In general, having the ability to record an "exit program" event, allows Sesame to be a good background batch processor.

Quote:
That is great!  You folks are too good. 

And thanks for letting me know I don't have to test this on the weekend.