I've seen in the FileMaker server MMC-console that it supports scripts for scheduling. Sounded like a really good idea I thought, but I can't find any information anywhere about how to use it or what kind of scripts it takes. I did try adding some basic things into a normal FileMaker file, placed it in the scripts folder and set a schedule for it. However, it didn't seem to do anything at all.

What have I missed? How are those script supposed to be set up? I'm having a hard time finding information about it on the web.

What I want to do is run automatic imports from our business system nightly to FMS that powers our webshop.

FMP: 8.5v1 (WinXP)

FMS: 8 Advanced (Win2k3)

Thankful for some assistance.

Hi Simon,

Welcome to the forums .

Unfortunately, the only scripts the admin console will support is essentially batch (.bat) scripts -- i.e. those designed to do something on the system vs. those that will actually do something in FileMaker - e.g. execute complex vbscripts to archive copies of backups and upload them to remote locations and other similar tasks.

YOu can actually trigger some scripts using (especially Custom) web publishing clients, but i don't think that's what you intended.

Server side scripting is a complex issue, and at such time as it might ever be implemented, it would require a lot of forethought and planning for the script to execute properly.

Steven

Ah... alright.

Moving on then. Installed an FMP client on the server machine that will handle the imports. With FMP 5 an import was "recorded" into the scripts (how it was to handle the fields and such) and it also recorded passwords for other files.

I'm thinking about having a trigger file (file is opened and triggers a script inside another file). Is enabling guest on the target the only way to let the trigger in and execute without prompting for username/password?

My way of thinking:

1. FTP Gets a file from the business system.

2. SED alters the data (making it tab-separated).

3A. Import-trigger.fp7 is launched.

3B. It triggers the import script inside Products.fp7

4. Import-trigger.fp7 is closed.

Got any better ideas?

Edited June 28, 200718 yr by Guest

[color:red]Don't run FileMaker Pro on the same machine as FileMaker Server at the same time.

Steven

Why? How is that a problem?

Because it has a high likelihood of damaging files, breaking file references, crashing the Server service, and otherwise creating problems.

Take a look at the Server Tech Brief on the FMI web site here.

Steven

I'm not sure which specs you wanted me to read there, there. Browsed around and reading bunches of docs but nothing mentioned having server and client on the same machine.

Also, I'm not sure we understand eachother correctly.

I'm not opening the .fp7-files directly in FileMaker Pro. I would absolutely understand if things broke if I did. No, the program (client) connects to the server using the same IP like all other clients.

If this can break the server, I must say I'm disappointed at how it is engineered.