I am thinking of moving the FMS solution to a hosted FM service.
Why? Is there a business critical reason to do that?
Thanks for you help
They have a local IT firm that controls the server. We have had many issues in even attempting to establish remote connectivity so I can tweak their solution from my office. The client has a FM9 based solution. They don’t use FM server at present. Just multiple concurrent connections inside their shop.
I would like to place FM Server on their local server, but based on past history I am leery at best. I have told them they need the server to have a dedicate static IP addy, which they claim to have but again remote wouldn’t work.
The local server houses multiple PDF, Pictures, etc for their 31000 client records. (Over 2 Tera Bytes of Files)
I am not a network guy, but I and my other clients have had good success with Point In Space.
Hope this explains things a bit better.
If all the users are on a LAN and can be granted "read" access by sharing the location to them. (And the shared folder is "mounted" under the same drive letter for every user--can be done with a batch file performed from FileMaker).
You could use insert picture with the "store a reference" option to insert references (file paths) to the images into container fields. This is the "old school" method of linking to container data and has limitations as I've spelled out. Don't know if external storage would work here as that's the better option if you can get it to work, but if not, the above option works.
"Store only a reference to the file" has just been deprecated (will be removed from a future version of FileMaker), so eventually this option will no longer work.
Reference: FileMaker Product Roadmap
I'm not too familiar with SuperContainer but it's another option worth looking at.
Thanks for the heads up. I can see reasons for deprecating this feature. I've only suggested this as an option if external storage can't be made to work as that's the better option here.
Hopefully, when/if they remove this feature, they upgrade or add other features to keep some functionality that would be lost if they just removed "store a reference" and made no other design changes.
I've opened a Product Suggestion on this topic to help raise awareness and so that others can add their uses of this feature (and maybe to suggest alternatives that would work if this feature were removed.)
Note that this has nothing to do with the issue in this discussion. It deals with other uses of "store a reference" that are darn handy.