image database

[kenneth2k1]

Hi

If I did use the container field approach...is it that bad? Will it end up crashing or will it take forever to load up?

I wouldn't say that this is bad. You will probably want to store all your pictures in a folder on one machine that will be the "Host." The other machines connect to the host. In the Host FM database, images are inserted and stored as a reference. If images are stored in the FM database and are NOT stored as reference, the size of your file will increase greatly as images are inserted. Some is OK, but many images WILL slow down operations in FM - believe me.

I'm very confused as to how to use the reference field? Any pointers on that?

If you store as a reference, you will not be able to export images, and if you delete the actual image from the HDD, it will not show in the FM container field. Storing a reference means it resides elsewhere on the HDD, not in your FM database, keeping the speed manageable.

I was referred to a plug in called the Troi File Plugin which I evaluated. It works great, and now I am going to purchase the full version soon because it works so good.

Ken

[mallikai]

Filemaker 5.5 cross platform...2 macs 3 ibm-comp.

I've got a picture folder that is 1.5 gigabytes and growing...

I would like to be able to share them via filamaker database...

I know it is not advisable to insert each pic in a container field. However, my questions are

1. If I did use the container field approach...is it that bad? Will it end up crashing or will it take forever to load up?

2. I'm very confused as to how to use the reference field? Any pointers on that?

thanks