The previous version of our filemaker application runs on a single amchine ( Filemaker v10) in this application we had a script who made a selection of records and saved this pdf file on the harddisk of that PC (in the scriptstep we had the relative path

file:kitchenprojects/$filepath

which saved the pdffile in the folder kitchenprojects on the hard disk of that PC;

$filepath is a variable that gives the pojectnumber.

so far so good.

Now we installed a server who linked together the PC's from our store in a small LAN. On this server we had a "common" drive on which all the pc's had access to and were files of general interest were placed.

On this server we installed and run filemaker server v10 with the same application as described above.

When executing the script mentioned above , I generate the same PDF file but i want to place those PDF's in a folder or map on the "common" drive (v: drive) of the server, and not on the harddrive from the client pc on which filemaker runs that moment.

i think i had to change the relative path in an absolute path, but with that

Bui I can't figure out the right syntaxis.

Second problem:

during evening hours and weekend I run the FM-application on the server over the internet and using "open remote" from my PC located at my home, That works. But with the script mentioned above i can figure out what the correct file path is to place the PDF in the same folder on the v: drive of the server.

any help or hints are very welcome

thnaks a lot

freddy

I believe what is happening, from a client perspective, is that the script is trying to save from the client-side to the V: folder. It is not looking at the server-side V: folder. The server is hosting the script, but FMP on the client is seeing the world through the client computer, as if it were running local.

Are (or can) the client machines be mapped to the common server folder as V: drives? Then, the script (when running from the client side) see the V: drive and save.

Am I understanding your question?