set _fixed_ Folder path for export

[Harald]

How do I force FM6 to export some files to a specioal folder (eg a networked folder on s:folder xfolder yfolder z).

Can I use the send message script step in order to set a windows shell command in order to change the current working direktoory (from now c: to then s:) before the export starts?

Harald

[QuinTech]

If you specify the path in your export, it should go there every time. I suppose if you temporarily lose your drive mapping, it may default back to the program directory, but i'm not sure.

Check out Wim Decorte's very neat solution if this does not exactly answer your question.

HTH,

Jerry

[Harald]

Pls, - in addition - let me explain the following:

These exports are triggered via scheduled tasks service on a Win2k-Server where I have access to FMP6 via a) Terminal Server or : VNC. What happens is the following:

It's true if defining and scripting the exports are done via TerminalServer Access it works perfectly to save the files to a networked drive. But if _only_ triggered via the scheduled task service the files are saved in the FMP6 directory.

But:

Strange enough, if - in addition to the TerminalServer Session - a _VNC_ session is opened, FMP6 will save the exported files to the networked drive...

Finally:

How do I use the Send Message Script step to force the Windows Shell to execute a command? I only used this script step to execute eg batch files or similar events ...

Thank you for your answer(s)!

Harald

[aaa]

In the Send Message Script step you can specify field which contents your Windows Shell execute command. I in this way start a command rar.exe for archiving.

[QuinTech]

It's true if defining and scripting the exports are done via TerminalServer Access it works perfectly to save the files to a networked drive. But if _only_ triggered via the scheduled task service the files are saved in the FMP6 directory.

I'm sorry, what is the scheduled task service? Are you talking about the Windows feature? If so, i'm not sure i understand how you're running a Filemaker script in this way. If i rush ahead and assume you have an fp5 that is run via the task scheduler and contains scripts, then the behavior should be the same whether run on "natural" Windows or Term Serv. If the behavior is not the same, are you sure that both the workstation and the TS client session have the same drive mappings?

How do I use the Send Message Script step to force the Windows Shell to execute a command? I only used this script step to execute eg batch files or similar events ...

It's right there in Wim's post. If you enter

cmd /c move /y c:backup.usr %userprofile%desktopmyFile.usr

in the Text portion of the Send Message step, it is just like going to the command line and typing

move /y c:backup.usr %userprofile%desktopmyFile.usr

The "cmd /c" portion of it just specifies to FM that it should use the DOS shell.

J

[Harald]

[QuinTech]

Sorry for the delay -- vacation time, you know.

I think i'm getting the picture. So if you log in to a Terminal Services session and open the file, what drive are the files saved to?

If, immediately after the FMP6 files are opened and the exports are saved, you run a batch file that moves the exports to the desired network drive, does that work? I only ask because that will help determine what is happening with regard to the file system. I find it surprising that FMP would not save to a network drive that is available to it. What i would expect is that, if FM is directed to save files to, say, the S: drive, but the S: drive is not available, then it would default to the program directory.

J