Did something change with the DBBarCode component from RB14.08 to RB15? We have several customers reporting that the bar code can not be scanned and the same form worked before loading RB15.
I tried a simple test here, created a report with a BarCode type 39 and printed it the printer using RB 14.08 and RB 15. The output looks identical to me. Perhaps you can try the same test.
- Nard Moseley Digital Metaphors www.digital-metaphors.com
Best regards,
Nard Moseley Digital Metaphors www.digital-metaphors.com
We tried that at 2 separate locations. They look the same when we try it here too. And, they both read fine from a hand held scanner, just not from one that is attached to an ATM. Do you know of any settings that changed in the update that may effect the way they are printed?
RB 15 renders the barcode to an intermediate metafile. A metafile records Windows GDI commands and then plays them back to the output device, so the result should be the same. The output looks identical in my testing.
- Nard Moseley Digital Metaphors www.digital-metaphors.com
Best regards,
Nard Moseley Digital Metaphors www.digital-metaphors.com
we have the same problem with the RB15.01 Build 2. But I think, that I have located the reason. With RB14 it was not necessary to "autosize" the Barcode. The Barcode always printed correctly.
Now in RB15 the Barcode-Elements have a fixed size and the barcode is cut, when the barcode is too long for the designed size and "autosize" is false.
It is essential for us, to have the old functionality. Otherwise we have to contact hundreds of our customers and redesign a lot of reports in their database.
Comments
They are using Type Code 39.
Deleting the component and adding it back to the form does not fix the
problem
Thanks,
Perry
I tried a simple test here, created a report with a BarCode type 39 and
printed it the printer using RB 14.08 and RB 15. The output looks identical
to me. Perhaps you can try the same test.
-
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
We tried that at 2 separate locations. They look the same when we try it
here too. And, they both read fine from a hand held scanner, just not from
one that is attached to an ATM.
Do you know of any settings that changed in the update that may effect the
way they are printed?
Thanks,
Perry
Windows GDI commands and then plays them back to the output device, so the
result should be the same. The output looks identical in my testing.
-
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
we have the same problem with the RB15.01 Build 2. But I think, that I have
located the reason. With RB14 it was not necessary to "autosize" the
Barcode. The Barcode always printed correctly.
Now in RB15 the Barcode-Elements have a fixed size and the barcode is cut,
when the barcode is too long for the designed size and "autosize" is false.
It is essential for us, to have the old functionality. Otherwise we have to
contact hundreds of our customers and redesign a lot of reports in their
database.
Thanks for your help!
Yours,
Michael Schustereder
I created a patch for RB 15.01 Build 2 that resolves this issue. Registered
RB 15.01 customers can email support@ and request the patch.
Thanks for reporting this issue.
Best regards,
-
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
thanks for your fast solution! It works perfect.
Yours,
Michael