Hi Lee,
In answer to your original question, there is a maximum file size.
It is 8 Terabytes. I have run programs up to a million records, but
it had to be kept really lean.
I would keep the photos in a separate file and access them only
through a relationship. Search description, get a selection and then
click on the selection to set a relational key and display the photo.
HTH
Dave McQueen
Thanks to all for your helpful hints. I'll explain a little more.
The file containing the photos will not be added to very often, if
at all. So that file will remain constant and will not be backed up,
apart from the first instant. All that is required is for a number
of people to access it searching by a description. My idea was to
use 2 files with the photo ID as the relationship.
One file with the photos and the with other only 2 fields, photo ID
and a brief description containing key words for each photo. Users
will only be searching for photo/s by inserting key words. No
backups each day will be necessary for either file, apart from a
copy of both when initially created.
All that is required is for a user to open the solution enter one or
more key words and have that photo/s displayed. There may be a
requirement to print that photo but that is all.
Does that make it an easier proposition to deal with ?
Lee
--
David A. McQueen
Lichen Software
Barrie, ON Canada
www.lichen-software.com
