I have a report-generating script that exports data to a temporary FP5 file and ultimately creates another, uniquely-named FP5 file containing summary records. It works fine in a single-user setting (where FM Server 5 isn't involved) but when I deploy it on the server, the attempt to create the temp file fails. I'm guessing this is because the server prohibits the creation of files, at least under some circumstances.

The location of the temp file doesn't matter to me; as far as the summary file is concerned, ideally it would be put on the client's computer but it could be stored somewhere on the server for the client to retrieve manually.

What approaches have other people taken for server-based databases which need to create temporary files on the server? (incidentally, my clients are all running FMP 6)

Thanks for your consideration,

Chap

Chap:

I would think that the script would still work, and that it would create the temp file on the client's computer - what exactly happens when you fire off the script?

-Stanley

Sorry to be so long responding -

When I run the script, at the point where it tries to Export a foundset to TempFile.fp5, I get the following message:

"TempFile.fp5" could not be created on this disk. Use a different name, make more room on the disk, unlock it, or use a different disk.

I assume that by "this disk" it means the server disk, not the client disk.

I'm not real clear about what a script considers to be "local" when it's in a file that's on a server, and is being invoked from a client. I have just assumed it used the CPU and disk of the server machine, and that the invoker's platform is irrelevant. I also assumed that the final report file would be created on the server and the client would have to manually move the report file across the network to her own machine. Certainly, having the finished product automatically end up on her desktop would be preferable!

Any advice or pointers would be greatly appreciated!

Chap