1 Reply Latest reply on Mar 17, 2009 11:02 AM by philmodjunk

    import/export path on client machines



      import/export path on client machines

      Your post

      I'm working with several scripts that export and import records, and run external applescripts.  Previously these have worked using relative paths for the file locations on the client machines, but now that we are hosting the databases with Filemaker Server, the scripts can't find the files.  All the client machines are set up the same way, with Filemaker in the applications folder and a folder within the Filemaker folder as a destination for these import/exports.


      I'm new to the Filemaker Server environment - what do I need to know?

        • 1. Re: import/export path on client machines

          So you moved your Database files to the server and now relative path references to external files don't work right?


          A relative path tells filemaker "open 'filename' that is stored in the same folder as I am". The key here is that "I" refers to the database file, not your applicaton. Hence your references no longer work.


          I can explain why they don't work. How to make them work in a server environment is more complicated. I think that if I were in your shoes, I'd install a copy of Filemaker Pro on your server, (don't run them both at the same time!), use it to open your file from it's new location, then relocate files/change their references paths until they work for you. Now quit FMP, host them on server and see if they work.


          For importing from files stored on client machines, you may need to open a hosted copy of your hosted database and update your scripts and data references to find the files on your client machine without using a relative path. Whether this works for you will depend a lot on how you have set up each client machine and what you are trying to do with these external references.


          Hope that helps.