Lebans or other Raw Binary Image Storage

  • Thread starter Thread starter kiln
  • Start date Start date
K

kiln

I'm interested in trying the raw binary format method for storing images
in Access 2000 tables. I think the lebans LoadSaveJpeg.zip is about
that, but it does not compile in Access 2000. Anyone know of other
sources for this method of image storage?
 
Larry Linson’s samples also include an illustration of this technique:
http://members.tripod.com/accdevel/

For other useful code examples search MS for ReadBlob and WriteBlob, and see 'The Access Web' for file-open
dialog implementations etc.

Finally, our commercial image control binds directly to binary fields in Access, and so needs no code.
It also features asynchronous decoding, lossless jpeg rotation, EXIF info viewer, TWAIN scanner/camera
integration and much more, and avoids the common configuration problems with graphics filters, OLE servers
etc.
http://www.ammara.com/
 
Since it was originally developed in Access2K it is probably a reference
issue on your side. A2K, unlike A97, does not have a reference set to
DAO. Once you set thsi reference the project will compile.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
 
Hi and thanks for responding. I'd not noticed the "read me first" form
before this am. It states that the app was writtin in A97 (you must have
forgotton that). There is a valid ref to dao...but maybe the problem is
that I hadn't known to place the intel dll into system (or probably it
should be system 32) but no that didn't help either.

Does compile at the report module (why it has a CmdLoad_Click() event?
Odd name since the event is not connected to a cmd button)


This line

strfName = m_cDib.FileDialog

does not compile as it needs a boolean arg. Many others like it fail
too, maybe all are around m_cDib.
 
You wonder why it does not work and you did not read the READMEFirst
Form included in the sample MDB?

THe sample Report is just a Form that was exported to a Report. The
CmdLoad_Click event and all other form related codes is commented out so
it does not affect anything. Delete it if you don't like it. I left it
in but commented out to show users the difference between using the code
in a Form versus a Report.

As I stated, and I was not mistaken, the code was developed in A2K. I
also test and release in A97 so I do not have to maintain two separate
versions.
The code in the sample Form and Report work. If they are not working for
you have either:
1) Failed to copy the INtell DLL to your System folder
2) Have modified the code in some manner.



--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
 
Aha, LoadSaveJpeg.zip is the one I downloaded that has the readme
form... and it's for A97 (try opening the contained mdb in A2k; and the
readmefirst form states that it was written in A97) and does not compile
in A2k (I can't see how it would compile in A97 either).
A2KLoadJpegGifVer30D.zip is the one that you must be referring to,
except that it has no read me first form. I mentioned that the file I
was working with was named LoadSaveJpeg.zip but you either didn't notice
or had forgotten that that file was not the A2k version. Sure enough,
A2KLoadJpegGifVer30D.zip is for A2k and compiles.

I'm not sure how I ended up with LoadSaveJpeg.zip...I think, because I
wasn't sure which of your many fine offerings pertained to the raw
binary storage issue, I did a search on that term on your site. The
resultant list had LoadSaveJpeg.zip and that's the one I downloaded.
It's not listed on your main index. Anyways that's the best I can
explain how I ended up with what was probably a early attempt or
something.

I had no intention to criticize you, I was just reporting events on my
end. The reason I did't even see the readme first form is because after
conversion to a2k, the notification that it wouldn't compile showed up
and I dove into a module to try to figure out what the deal was. I
didn't look at the forms till much later.
 
We are both getting mixed up. Honestly, I thought you were crazy<grin>
because my A2K version does not contain the converted Form to Report you
were looking at with the uncommented out code. This is the kind of stuff
that happens when you maintain two different verions(A2K and A97) on two
different machines.

The code you want is in LoadSaveJpeg.
http://www.lebans.com/loadsavejpeg.htm
The code was developed in A2K. When I converted it to A97 I always
compile it and test in A97. I inadvertently left in the report that is
causing you the problems at compile time. Just delete it and the sample
Form will work.

The original A2K source MDB has a functioning sample Report that works.
I have published new A2k and A97 versions tonight. If you have been to
my Web site recently you may have to click on the REFRESH button within
your Browser to see the new files.

Sorry for the mixup. As penance, I will modify this solution to use the
Microsoft GDI+ DLL to enable you to Load/Save Jpeg, Tif, BMP, EMF, WMF,
GIF and BMP in the next few days.
:-)

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
 
Well, that would be cool. You're the best, really. Sans the report that
converted mdb does compile. This is going to be a great learning
resource for me; I've not needed to do much with images before. A new
project will need sophisticated linking to images stored in the file
system, but one part of it really would be better with the images in
tables. If I can get the hang of this technique, it's going to be a big
plus.

Thanks again
 
Back
Top