Hi..

How can i view/download container fields in fmClient via remote connection to server over fmnet:/ (no mounted network path, as the server is on the other side of the world to the clients)..

I have read that this is possible via client as XML/WEB? Is it possible via fm client?

Solutions anyone?

My database is starting to balloon with embedded containers.

All media is added from remote locations and is now

x3000+ jpeg width=350 thumbnails & x1000+ (simple single sheet ).xls/.doc/.txt files with only two weeks use and third of this is from fmtouch - its been busy with just a two weeks dev-lead!)

is my choice either mount remote volume(VPN - with matched mount names) or supercontainer plug?

thanks

rafal

Edited February 12, 201015 yr by Guest

Do look at SuperContainer.

Not sure exactly what it is you are asking. If a user has FM client then yes they can see what's in the container fields and they can export the contents and use it.

Using XML and similar web technologies you can also "download" the container content without using FM client.

Not sure exactly what it is you are asking.

How can i view referenced container files in a filemaker client, if i don't have access to the container files via Finder(in osx) or the file browser(in win).

idea? Can I put theses container files in the FMserver's web file folder and then use a url in filemaker container field as reference to this url?

idea? Can I put theses container files in the FMserver's web file folder and then use a url in filemaker container field as reference to this url?

FM won't accept a "http" file specification, it must be a OS level access that is available to the stored file.

If you want your users to be able to download the images via FM clients then you will probably need to store the images in the DB (i.e. NOT referenced) - otherwise you must provide an OS level access storage point for the images.

Consider also SuperContainer plugin.

We've used FTPeek and have the files on an FTP server. But they're not images, just pdfs. For images, I would image SuperContainer would provide more functionality. All roads lead to 360works.

Thanks for your suggestions. I think we will go with a vpn solution. (its free and we all ready have the system in place to mount/access all hosts/volumes from our remote laptops).

If we were referencing actual full size image-files in fm then superC might be a good idea, but as all images are thumbnails created from various wierd no qt formats via command-line/applescript routines(sane-scanner/exif-tool/sips/qt/ffmpeg). SuperC an unnecessary complication.

Wish filemaker natively allowed access to http referenced container images in a client, seeing as it can all ready serve container fields via http/xml & web publishing..

Edited February 13, 201015 yr by Guest

Watch out with Apple clients on VPN. The VPN will lose the "afp:" protocol, although you can still connect via direct IP address. That means that your container references must be setup with IP addresses as part of their filepath - so the referenced files are strongly bound to the network and the hosting machine.

If you move the files you must assign the same IP address to the host, or setup a calculated filepath that can have the IP address changed if necessary.

I cannot comment for Windows clients using "smb:" protocol.

thanks for the afp: tip.

I think we are using nfs: so it should be ok, but will check.

Err.. maybe not, because VPN also throws away smb protocol too for Apple clients - I suspect the same fate for nfs.

Edited February 14, 201015 yr by Guest