Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 8869 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

my solution is hosted by FileMaker Server 3.04 in an apple talk network. a script should update a file by importing datas from another file. everytime this script is running I get an error message saying FileMaker could not find the original file. is it a bug? what can I do? appreciating every hint

jean paul

Posted

FileMaker Server version does not have the ability to directly run scripts. The script is actually running on the client machine. The "import" script step is looking for the file on the client machine. If the source file for the import is on the server computer, it won't be found. (I'm assuming by script you mean a FM script and not an AppleScript and that the import is probably running as a startup operation in a database file). -bd

Posted

I am using FMP 4.0v3 as my server software, this is what I have done.

The problem is that the script runs on the "guest" machine, not the host. So when they try to import, it looks for the file on the guest's computer.

I work around this problem by making a script that performs the import -- the trick here is getting it to run on the *host* not the guest machine, do this by making it a startup script (use the Status(CurrentMultiUserStatus) function so it only runs on the host machine).

The only down side is that the script only runs whenever the db is opened on the server. For me, my imports can wait a few days until I back up the machine.

Update!!!

Last week, after posting this, I began to think about the issue of getting scripts to run on the server, not the client machine (specifically I wanted to run a script that closed databases so I could back them up, then run another script to open them again). Well, I worked out how to do it!

1) Make a database with the scripts needed to close and open the databases (or perform whatever task you want).

2) Turn on web companion and activate web sharing.

3) Add a password to the database -- you don't want to let just *anybody* shut down your server!

4) Write custom HTML format files that use the -Script CDML tags that perform the scripts!

I can now open and close my databases remotely through a simple web interface.

[This message has been edited by Vaughan (edited August 20, 2000).]

This topic is 8869 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.