Has anyone ever been able to store JPEG images inside a D3 database?
This would have to be D3/NT , on Rel. 7.2.1. I have a need to
"associate" images with products that are for sale on the web. I seem
to remember having seen something a while back that stated this was
possible.

Thanks,

JJCSR

Store the image in hex: img = OCONV(img,'MX')

Don't store the images in D3. Store them anywhere else and link to
them from D3. I recommend an application-level pointer to a domain or
server, and then in your product master records just store a filename
or relative path. This way you don't need to rework hardcoded
pathnames if you decide to change your architecture. Your app softare
can generate links or URLs as appropriate.

HTH
T

"JJCSR" wrote:

I've done this exact thing a couple of times for jpg mugshots, storing mp3
and .wav items and .avi video.

If you decide that for some reason you MUST store the jpg item inside pick,
use the NT_BIN host name and do something like this:

to copy to pick
COPY nt_bin:/path/ picturename.jpg
topickfilename

Item will be copied to the file as a "binary" item. You won't be able to
edit it or anything, but you'll be able to save it in a filesave. To Pick,
it looks like object code.

To use it, copy it back into windows

COPY pickfilename picturename (o
toNT_BIN:/path picturename.jpg

Mark Brown

"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote

Hi

FlashGUI library have such tools.
GP_Term.Lib have BCPTOPC and BCPTOSRV TCL commands.
GP.FileXXXX subbroutines can work with binary data.
You can show images from Your GreenScreen application directly without
calling any PC exe

Regards,
Grigory

Thanks to all who replied to my posting, reharding JPEG images being
stored in D3. It so happens that there is a change in method being
used, and, instead, I will just be capturing the image names, not the
image itself. The actual image will be stored in a MySQL file on our
web site. Through the use of OPENDB, I can get to the image file, if
necessary.

Again, thanks and happy Holidays to all.

Jim Cronin

Mark Brown wrote:

Jim, I don't want to change any visition there but I'm wondering why
it's necessary to store the images in a database at all, compared to a
file system. I can't see any benefit and the overhead seems hugely
against doing such a thing. Maybe we can learn something here.

Thanks.
T

"JJCSR" wrote:

Tony,

I would think wide dispersion versus concentration. With the pictures
stored in the file system, you basically have to open each picture
individually, as opposed to having the pictures stored in a single
"database" which in some cases is open throughout the life of the process.
I would also think the overhead of openning several pictures per page (as
with catalogs) vs the single opendb and a recordset of picture blobs would
show clear advantages to storing the pictures as records, especially if you
can "bind" the picture objects to the recoreset.

Mark


"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote