big size database ... performance?

[alopas]

Hi,

I am making a database for my department using FM 5.5, that includes text, calculations and small graphic fields. I have been asked about the possibility of making a database for another department. This one should include up to 5 graphics per record, and the size of each graphic could be up to 1 Megabyte big. If I made one database per season, each one would have up to 300 records, that makes the size of each database about 1500 Megabytes big. This database would be used by 10 persons at the same time (through an Apple server), that would need to drag drawings from either Illustrator or Photoshop into FM. Besides, different users would need to print records at the same time, sending them to the same printer. The main goal of doing this new database would be saving time, and my main concern is if a database such big used by 10 persons would go slowly. I would appreciate any advises.

Thanks in advance.

[LiveOak]

I guess I'm not sure why you would want to drag 1MB images into FM. When pasting an image into FM it is converted to Pict. Unless you are trying to use FM to store Pict images, it is a much better idea to either copy down sampled images into FM (screen display is only 72 dpi) or import the reference to the image into FM. If you just import a reference to an image in another folder, the size of the FM database will not increase very much at all with each new image.

-bd

[alopas]

Importing a reference solves all the problem, thanks a lot. (Still a beginner...)