New Versions bug


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ] [ FAQ ]

Posted by Brian Levantine on Wed, 1 Oct 2003 08:46:30 :

New Versions bugI recently ( last week ) upgraded all my Comet versions. =
Actually this took place in an attempt to pin down Steve's Ultra Edit =
compile problem. It did bring about a problem

though. In my Fonts folder I have a TrueType 16-bit barcode font 3 of =
9 Barcode. I have used this for bar-coding inventory labels. Any of =
my bar-coded #CFORM-based

programs run and print barcodes. However, if I simply compile a new =
object from those programs, the new object program no longer prints the =
barcode, it just prints the

ascii character data. For example, I'd send out *100019* as data =
and it would print a bar-code. Under a newly compiled program, it =
actually now prints out *100019*.

Any Ideas? Unfortunately, this has occurred in the middle of the =
installation of a new bar-code labelling system at Carleton V. I'd love =
to hear of a solution or fix - if not I'll=20

probably have to backgrade to the 03.02 of the WinDev and .320 of =
Comet2003. Thanks in advance, Tom.=20




Follow Ups: