I am very new with FM and FileServer. Sorry in advance for a silly question, but I can't find a direct reference to this problem.

I created a database on my (client) computer with a container field that has pdf file links - actual pdf files are not in the database.

I installed FileServer on our Server computer fine, loaded the database on the Server and can access the database as a client no problem, but when trying to open the pdf file link, it cannot locate it. Any easy answer to where the pdf files need to be or how I tell the server where they are?

Thanks!

You mean you had them "referenced"? I.e. not actually stored in the database. The thing is when you add the file, all filemaker does is stores the filepath. Which means that when you move the filemaker file on to the server, the filepaths which were likely local to your previous machines are no longer valid. For example if you stored a file as c:filepath.pdf filemaker would search for that at that path. And that file doesnt exist on your server so... no file.

I personally use dynamic file paths and calculations resulting as a container field to present my images exactly because of this issue.

} Thank you very much for your suggestion!

I am having a similar problem. Can you please explain what you mean by dynamic filepaths and calculations?

Regards

Dynamic meaning the initial part of the filepath up to the point where the actual filename is picked up, particular to the current record. I.e. you could have a folder called images and in that folder jpeg's with filenames that relate to the unique serial number of a particular record.

i.e. where xxxxx is your unique serial number.

...images/xxxxx.jpg

The elipses (the ...) represents the "dynamic" part of your filepath which you can store in a global field somewhere. I.e. you point your calculation to:

Table::DynamicPath & "/images/" & Table::id_Unique

In summary we need 5 things:

A) A global field with the initial part of the filepath.

: A calculation field with result container to pick up the picture particular to that record (use the above calculation)

C) A unique serial id for each record

D) A folder called images or whatever you want really.

E) Finally a hidden container field to import an image temporarily, then export it to your dynamic filepath location and name it using your current unique record, then clearing the container field.

Once again, i sort of lose track in long posts, so if something is unclear, just drop another post.

~Genx