Hi,

I have a client that is getting ready to upgrade their existing FM (7) solution and they are asking for some advice. They design/print stickers. So, there are graphics files involved here. At the moment, I have them talked into having a stand alone machine to run Server 8.0v4 (with Mac OSX Server as operating system). We are trying now to decide about the best performance options for storing (or holding references) to the graphics. I essentially outlined two options for them:

1 - Hold the graphics (max 72 dpi) in the FM database container fields. But they'd have to save them as well on another drive where the art guy would access them and edit them as necessary using Adobe Illustrator. So I see some duplication/overhead issues there. Also the issue of having to be sure to always remember to update the graphics in both places if/when they changes.

2 - Store only a reference to the graphics. This one has always seemed to present problems for me because the users cannot guarantee that they will not ever change the path...and when the path is changed...well, you know what happens.

So my questions are as follows: what can the Troi File plug-in do for me? It seems that it does allow you to store only a reference, but also somehow hold a thumbnail? Can someone elaborate on that for me? What happens if/when the graphic is updated? What happens when the path is changed?

Also, we are getting some advice from the hardware guy that we might be better off having one Mac Mini to hold the operating system and the FM Server software, but then hold the actual database file (presumably with the graphics contained in container fields) in an external drive (+300gigs) connected by firewire. Is that a good idea? Would it be slower or faster to refresh/present the graphics to the users??

Thanks for any and all input.

Kate Schneider

Also, we are getting some advice from the hardware guy that we might be better off having one Mac Mini to hold the operating system and the FM Server software, but then hold the actual database file (presumably with the graphics contained in container fields) in an external drive (+300gigs) connected by firewire. Is that a good idea? Would it be slower or faster to refresh/present the graphics to the users??

This is bad and incorrect advice. I have no clue why a hardware consultant that knows anything about how FileMaker Server works would recommend such a course of action.

[color:red]Do not use a miniMac as a FileMaker Server CPU.

Steven

Hey Kate, how many client connections are we talking about here? How big (KB) are the typical graphics files? How many graphics files are you anticipating?

The FileMaker databases should reside on a fast drive with a fast bus. The mini's internal drive is not very fast, and the firewire 400 port is not very fast either. This is why the mini is not a good machine for a FileMaker server.

Small organization...5 users currently; 7 max -- maybe in the next year or two...