Is this a Limitation to Container Fields?

[jimkent]

I have a Photo Catalog Database that stores family photos from a designated folder on a Hard Drive. These photos are displayed by and import routine that adds the file reference to a container field. The problem I have is if I move my database file to some other drive or folder, or even rename the Drive Volume, I loose the file reference. Somewhat understandable... But is there anyway I can "re-attach" the references without re-importing all the images? I have over 9000 images. That would not be fun.

I could switch it to a web viewer but the images are quite large, and a Container Field can be manipulated so the image will be resized to the field size. The Web Viewer just shows it full size. If I was to embed the image, the 9000 images would make the DB file ginormous.

Is this a limitation of a Container Field? Is there anyway around this? I'm running FMA 10, does 11 fix this or is that just wishful thinking?

Thanks,

Jim

[Ocean West]

SuperContainer to the rescue!

I would seriously look in to using SuperContainer by 360works for anything dealing with container data.

http://www.360works.com/supercontainer/

The beauty of SuperContainer is that it will auto create thumbnails for viewing in either a web viewer or using the companion plugin, to a calculated container field.

because the path to the server or standalone is URL all computers on the network can see the data.