Where does FMPSMLRESULT file go?

[*susan*]

This is such a basic question, but here goes.

I am using an xml file for creating an export with the correct encoding. In single user mode, the file can live on my harddrive and the routine works as expected.

However, these files will be hosted, and I would like the xml file to live on the server only. Where can this file live and be available to hosted files [and consequently the users]? What option would I select in the XML selection dialog?

Any help would be appreciated. Many thanks....

*susan*

[IdealData]

If this is a user initiated action then they must already be connected to a share point on the server - then they can specify that this is the destination.

FMServer 10 also permits record export but you'll need to use a server side FMS script and target the DocumentsPath using a scripted $var. The DocumentsPath on the server is NOT "My Documents" but is rooted in the FileMaker Server directory structure.

[*susan*]

Oh dear. That didn't really make sense to me.

The routine is run by an end-user. They select the 'export' button. The export records step looks like this:

[No dialog: "$filename"; "FMPXMLRESULT"; "encode.xml"; unicode (UTF-8)]

the Specify XML and XSL Options dialog has "Use XSL style sheet" check, and at the moment, I have file pointed to 'encode.xml'.

I have tried to embed the xml into a field. That didn't work. I have tried to point to the file on a website, and if this is possible, I am not creating the right path.

I guess the question I need to start with is, Is this possible? To have an end user create an export using XML that sends a file to their desktop without having the xml file on their hard drive? And then if it is possible, to figure out how.

Thanks....

*susan*

[comment]

The XSLT stylesheet can live in any location on the network that's accessible by the user, or it can be hosted on the web (as long as it's available by a HTTP GET request).

Another option is to store the stylesheet in a container field, and export it - before the "real" export - to a known location on the user's system, e.g. the temp folder.

Note: it would be less confusing if your stylesheet were named with the standard .xsl extension.