Is it possible to create a runtime that can create documents from
within it and have it handle these documents like typical document
based apps do.

Problems:
Cannot create OPEN menu item
Primary DB will open when other DB are opened.

Are there any work around that could make this more user friendly.

Thanks
Vincent

In article <1132100345.134698.314830 (AT) g44g2000cwa (DOT) googlegroups.com>,
"vcirilli" <vcirilli (AT) dslextreme (DOT) com> wrote:

Errr ... ?|

If you're asking if a Runtime solution can create new / blank database
files, then the answer is no. You have to buy FileMaker itself to be
able to do that. The ability to create a standalone Runtime solution is
only to allow you to create a solution for someone who doesn't have
FileMaker.

The Runtime application is "tied" to a particular set of solution
database files, but there's no reason you (as the developer with the
full FileMaker) can't add other files to use the same Runtime
application.


Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

Not blank but clones of the primary with no records.

But thanks anyway I solved it.

Vincent,
As you raised the question, it would be nice - not to say polite - to
give us the way you solved it.
Remi-Noel


"vcirilli" <vcirilli (AT) dslextreme (DOT) com> a écrit dans le message de news:
1132191776.157341.119600 (AT) z14g20...oglegroups.com...

In article <1132191776.157341.119600 (AT) z14g2000cwz (DOT) googlegroups.com>,
"vcirilli" <vcirilli (AT) dslextreme (DOT) com> wrote:

If you're using global container fields to store any graphics (or even
music, etc.), then you have to be careful with the Save As Clone option
.... not only does it not save any records, but it looses the data from
the Global fields as well. \



Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

Remi-Noel Menegaux wrote:

Sorry didn't think anyone was interested.
Maybe using solved was a bit overstated , more of a workaround.
When the runtime app is opened via the runtime or primary documents, I
prompt to create a new db or open an existing. When the new or
existing db opens it closes the primary db. So the primary db never
really gets used to store records it's basically just a template. In
the case where a newly created db is
used to open the app both the intended db and primary db opens, luckily
the primary open after the
intended so there's a branch in the open script that closes the primary
leaving just the intended open.
The primary is recognized using a global, which is set true before
creating the runtime.
Using save clone no rec's to create new db from the runtime
automatically clears the global which
differentiates the two types of files.

There is a issue I'm dealing with - in the save a copy as script step I
can't hard code the open after save checkbox which leaves it open to
user error.