Is there a way to import data from an XML file, but using an XSLT sheet that
is imbedded in the FileMaker solution?
The normal way to write such a script step is to specify a file containing
the XML data, then to specify a separate XSL file that tells FM how to
interpret the XML.
I would like to avoid using a text file separate from the solution, so that
the whole solution, including the XSL, is in one file.
-
In the Script step Import Records using XML, the ³Specify XML and XSL
Options² dialog gives you the option of specifying a file path or a
Calculation. What would be nice is to make the calculation reference a
container field that contains the text of the Style Sheet.
-
ScriptMaker lets me specify such a field, but it returns a runtime error. Has
anyone done this?

What I have done in the past to resolve a similar problems, in a
Windows environment

- Create a container field and store your XSLT stylesheet in the
container
- Export Field contents of the container field with the XSLT
stylesheet on demand (when an import/export of FileMaker data need to
be performed). Export for example to the desktop. Use a path variable
to point to the XSLT stylesheet in your Import or Export script steps.
- You could write a VBScript/Applescript to delete the exported XSLT
stylesheet

HTH

Jeroen

On Feb 4, 10:35 am, Al Hatch <h... (AT) waywewill (DOT) com> wrote:

On Sun, 4 Feb 2007 01:35:32 -0800, Al Hatch wrote
(in article <0001HW.C1EAE8E400CC93D4F0203648 (AT) news (DOT) covad.net>):

There is no way the "Import XML" step can use an embedded style sheet.
However, you can export an embedded style sheet, use the resulting file, then
delete that file before exiting your script.

You could also delete the file using the Export Records script step.
First empty your found set, by omitting all records for example. Then
call Export Records with the file you want deleted as the destination
and the Perform Without Dialog box checked. This will delete the file.
Kind of a hack, but an interesting technique.

Nate

On Mon, 5 Feb 2007 05:53:10 -0800, NScheffey wrote
(in article <1170683590.411081.207360 (AT) a75g2000cwd (DOT) googlegroups.com>):

Actually, I've refined your suggestions a little. As long as you're going to
delete the file anyway (or overwrite it), why not replace it with a short log
of what your script just did (number of records created, data and time,
etc.)? Using the same filename, of course.
That's my new method, and I'm sticking to it.