Thanks everyone for the suggestions. I have a lot to think about. I like w00dy's idea if it doesn't bump into the 2gb limit Paul mentions, and even then I'm sure I can figure out a work-around.
And for the record I did create an app a few years ago where I ignored the common advice and used General fields for images. My company's admissions department had 26 separate forms that were filled out when a patient was admitted and they were doing it all with pen and paper. So, I scanned each form into a separate General field. Then I created 26 separate screens and used the images as the background for the screen (OLE) and superimposed text input fields over the image. And finally I created 26 separate reports (FRX) to print them out. This app has been on a network share and used by two endusers every day for over 5 years without a problem.
I'm not sure where the problem is regarding General fields and images. I've never experienced it.
Ken
------ Original Message ------ From: "Stephen Russell" srussell705@gmail.com To: "ProFox Email List" profox@leafe.com Sent: 8/16/2022 11:33:58 AM Subject: Re: Pictures in a table
In some environments, you have to store the document in a db because you are on a large network. That path may not correspond to others say viewing an XRay and getting an opinion from a team in Japan, Australia, etc.
You also have to have killer backups of that folder where they are kept as well.
Our rule is to convert all "visual" objects to pdf and insert that into the db. I have to store vendor publications on carcinogens with our raw materials, and have plants all over the world have access to that if a customer asks for it.
On Tue, Aug 16, 2022 at 9:33 AM Alan Bourke alanpbourke@fastmail.fm wrote:
IMO don't ever store binary objects in a relational database table. Store a relative path and filename from a root disk location.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]