Hey Ted.
Thanks, yep it's been a while.
We can always count on you for a detailed explanation. I think I
understand the issue now. And since my app uses no external programs to
deal with the images, I shouldn't run into that problem. Unfortunately I
got rid of my tons of Fox books (including
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. I
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 Ge
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
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
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: ht
Hi Ken,
There is now that funny thing called BLOB-Field. Your advice was relevant
for those dark times where we only had that General fieldtype. Now, the BLOB
is a Memofield like the General-Field, but it just stores Binary data
without any OLE-Information. You basically write the picture-file cont
6 matches
Mail list logo