I have not seen the following method described before, so I will present it as a way to distribute any kind of file from a FileMaker server to connected clients. A typical example would be distributing a new version of a FileMaker interface file to all users of a FileMaker Server. (It is worth while to run FileMaker interface (or GUI) files locally on the client, while the data file(s) reside on the FileMaker server).

1. On the FileMaker server (Mac) all plug-ins to AutoUpdate should be placed in this folder: /Library/FileMaker Server/Data/Databases/AutoUpdate/.

2. Create a new folder inside the AutoUpdate folder to store the Interface file to be distributed to clients: /Library/FileMaker Server/Data/Databases/AutoUpdate/Interface/

3. Create a folder inside the Interface folder with the version number of the FileMaker Interface file: /Library/FileMaker Server/Data/Databases/AutoUpdate/Interface/1.1/ (there may be a number of version files inside the Interface folder.

4. Make a zip copy of your FileMaker Interface file (right click on Mac an select compressed archive ... ). Rename the compressed archive to "Interface.fmplugin.tar". and place the renamed file in /Library/FileMaker Server/Data/Databases/AutoUpdate/Interface/1.1/Interface.fmplugin.tar (the name of the file must match the name given to the folder in (2)).

...

5. When you start your local Interface file then ask FileMaker server for a list of the available versions of the Interface file on the server by: [color:blue]FMSAUC_FindPlugIn ( "Interface" ). This command will return a space delimited list of all available versions of Interface file in the /Library/FileMaker Server/Data/Databases/AutoUpdate/Interface/ folder. Check that your local version matches the highest version of the server. If not, download the newest version.

6. Downloading of version 1.2 requires the command: [color:blue]FMSAUC_UpdatePlugIn ( "Interface 1.2" ). This command will download the zipped version of Interface file 1.2 and place it in /Users/MyName/Library/Application Support/FileMaker/Extensions/Saved/ in unzipped version and with its original name (example "MyInterface.fp7"). The datatransfer and unzipping is very fast.

7. Now you can use a helper file to close the current Interface version, move the new downloaded version from /Users/MyName/Library/Application Support/FileMaker/Extensions/Saved/MyInterface.fp7 to the same place as the old MyInterface.fp7 (and overwrite it). Then start the new version, and you will be running a new version without any user interaction. The file movement can be done by Troi_File or a similar plug-in.

8. I have not tested this procedure yet on the Windows platform but can see no reason for it should fail there.

This method will allow you to download any kind of file from a FileMaker server to a client if you just disguise the file as a plugin. No ftp is required.

Note1: You will receive a -1 error to the F[color:blue]MSAUC_UpdatePlugIn ( "Interface 1.2" ) instruction, because FileMaker can not finish installation of the downloaded disguised plugin. Which actually is quite acceptable when you really are downloading something else.

Note2: The method described is for version 9.

Best regards

Mogens Brun

FMintegrator

Thanks for this tip.. it works just fine on Mac as you said, but do you have any idea why the same file ran on a Windows machine does not see the available interface files for downloading?

UPDATE:

If I create an alias of the tar file and name the alias "Interface.fmx" it's seen by the windows client, but an error happens on downloading(error#6)..

So it seems that Windows version of FMP9 is only able to download a proper valid fmx file.

I tried changing the file extension, and the plugin downloads, but in a plugin form, and when trying to reverting the file type when on windows to .fp7, the file is corrupted and can't be opened..

Edited October 31, 200817 yr by Guest
Added details