Ken: Welcome back, long time no see.
HackFox talks about general fields here: https://hackfox.github.io/section5/s5c1.html As a general rule (pun intended), general fields were all part of the grand plan of Object Linking and Embedding, which is such a great idea they renamed it several times. It depends on a document type like ".JPG" being linked to a specific application, say Paintbrush or Microsoft Photo Editor, via the Registry. If you install a third party tool for image manipulation, it might overwrite the registry association, and if one user saves a file now associated with "Fred's Awesome Editor" the next user, still using Paintbrush, won't be able to use it. To help this process along, sometimes a major update or replacement with a new version can break (er, "reset to default") the associations. Or the Registry itself can become corrupt and the link is lost. So, OLE can be fragile. Hope that helps! On Tue, Aug 16, 2022 at 3:57 PM Ken Watkins <kwat2...@gmail.com> wrote: > > 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" <srussell...@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 <alanpbou...@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] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CACW6n4sQ9iBWDCKNfkaTK1FYb9ecin-hfC7crN_qcOFU76h=z...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
