Blob Image on Report not picking the correct image

[TinyNinja]

I need help with my Blob Image. I have Order Numbers that I'm creating Barcodes for and need to throw the correct barcode image on the correct order number report. In my testing, I have 3 orders and 3 different barcodes. When the reports get created, it only used barcode A for all 3 orders instead of matching each barcode with the correct order.

Any thoughts on solutions?

The setup

The Entry code to grab the images

The variable

The picture

Report 1

Report 2

Report 3

 

[mJindrova]

Hi,

Specify Controls Source as: CreateImageOnFly(BARNAME).
Variable BlobImage can you drop and "On Entry" expression can you clear too.

[pre]
PROCEDURE CreateImageOnFly
LPARAM m.lbBARNAME
LOCAL m.loImage
m.loImage=CREATEOBJECT("Image")
m.loImage.PictureVal=m.lbBARNAME
RETURN loImage
ENDPROC
[/pre]

mJindrova

 

[Chris Miller]

I'd say on entry doesn't happen as often as you think. To print something that changes with every record, well, use the expression. mJindrova has a good idea for that.

Microsft posted this KB for how to print blobs:

https://www.betaarchive.com/wiki/index.php/Microsoft_KB_Archive/895602

It's a bit involved to do it as they implemnented it with a reportlistener and its BeforeBand event, but look at the comment:

*--------------------------------
*-- There has to be some way of redrawing the
*-- picture in the IMAGE class as the record pointer
*-- in the report's driving cursor changes; it does not occur
*-- automatically. [highlight #FCE94F]This could be done by a UDF() in the PrintWhen[/highlight]
*-- of the OLE Bound control on the report, or as is illustrated here,
*-- by a Report Listener BEFOREBAND() Event.

There's another idea to (mis) use the PrintWhen condition to update the image and have a simple static expression of the image object, which changes by PrintWhen.
Notice that variables you use in a report don't need to be created in the report variables section, it can be any local variable you define before running the report. The only advantage of variables created and updated by the report itself is encapsulation. The only real need is for calculation types other than none, though.

To clarify UDF is just meaning user define function. Can be anything that does something to the image variable and returns .T. in the end. So it could also be ýour EXECSCRIPT().



Chriss

 

[mjcmkrsr]

Hi TinyNinja,

Is there a specific reason to store your barcode files in BLOB fields? If not you could simply point to the picture files in your report (see demo code attached)

MarK

 

[TinyNinja]

I've made a big rookie mistake. I have be pointing at my first table I use rather than the view I created that is holding all the necessary info for the report. I finally realized it when I browsed the loops happening. Now that I'm pointing at the correct data the Picture & Blob methods both are working.

Hey mJindrova, Thank you for your suggestion and your code helped me realize my mistake.

Hey Chris, Thank you for linking to that article. I have saved it for future reference. Thank you for clarifying, it makes sense and has been helpful.

Hey mjcmkrsr, there isn't really any specific reason for the BLOB field. I had used it at my old job and figured it worked then so I should use it again. Thank you for your demo code, I have changed my code to point to the picture since the image looks crisper than the blob look.

I knew this problem had to be like 1 thing I was missing and ended up being the case. Thank you all!