Hello

I can print the right barcode on the paper,
but on the screen the barcode is wrong.

I use Code128.ttf from grandzebu.net
and i work with oem in xbase++
I have tested some conversions ansi<=>oem , nothing, i didnt find the 
mistake.
If i copy the calculated codestring to word the barcode is displayed well.

Any idea whats wrong?

Reagards
Roland

Additional Informations:

Some ansi/oem-problems solved
BUT
when i use GraStringAt the BarCode is displayed OK,
when i use XbpStatic the BarCode is wrong
(see attached pictures).
The wrong BarCode has three additional bars at beginnig.
If i hide them the scan is ok.

Any idea whats wrong?

Regards
Roland 

Problem encircled:

Attached is a screen shot that show the bar code results of using XbpStatic 
and GraStringAt among each other.
GraStringAt shows the right bar code.
XbpStatic seams to have problems with the space before the first bar.
The space is coming automatically from the bar code font.

Roland

"Roland Gentner" <rg@gentner.net> schrieb im Newsbeitrag 
news:6c483b41$5c92b3fc$9131@news.alaska-software.com...
> Additional Informations:
>
> Some ansi/oem-problems solved
> BUT
> when i use GraStringAt the BarCode is displayed OK,
> when i use XbpStatic the BarCode is wrong
> (see attached pictures).
> The wrong BarCode has three additional bars at beginnig.
> If i hide them the scan is ok.
>
> Any idea whats wrong?
>
> Regards
> Roland
>
>
> 

Have you tried alltrim() ?

On 9/14/2010 1:21 AM, Roland Gentner wrote:
> Problem encircled:
>
> Attached is a screen shot that show the bar code results of using XbpStatic
> and GraStringAt among each other.
> GraStringAt shows the right bar code.
> XbpStatic seams to have problems with the space before the first bar.
> The space is coming automatically from the bar code font.
>
> Roland
>
> "Roland Gentner"<rg@gentner.net>  schrieb im Newsbeitrag
> news:6c483b41$5c92b3fc$9131@news.alaska-software.com...
>    
>> Additional Informations:
>>
>> Some ansi/oem-problems solved
>> BUT
>> when i use GraStringAt the BarCode is displayed OK,
>> when i use XbpStatic the BarCode is wrong
>> (see attached pictures).
>> The wrong BarCode has three additional bars at beginnig.
>> If i hide them the scan is ok.
>>
>> Any idea whats wrong?
>>
>> Regards
>> Roland
>>
>>
>>
>>      
>
>

Hello Joe - alltrim() did not help


"Joe Carrick" <joe.carrick@dslextreme.com> schrieb im Newsbeitrag 
news:15b4d998$4af82211$8291@news.alaska-software.com...
> Have you tried alltrim() ?
>
> On 9/14/2010 1:21 AM, Roland Gentner wrote:
>> Problem encircled:
>>
>> Attached is a screen shot that show the bar code results of using 
>> XbpStatic
>> and GraStringAt among each other.
>> GraStringAt shows the right bar code.
>> XbpStatic seams to have problems with the space before the first bar.
>> The space is coming automatically from the bar code font.
>>
>> Roland
>>
>> "Roland Gentner"<rg@gentner.net>  schrieb im Newsbeitrag
>> news:6c483b41$5c92b3fc$9131@news.alaska-software.com...
>>
>>> Additional Informations:
>>>
>>> Some ansi/oem-problems solved
>>> BUT
>>> when i use GraStringAt the BarCode is displayed OK,
>>> when i use XbpStatic the BarCode is wrong
>>> (see attached pictures).
>>> The wrong BarCode has three additional bars at beginnig.
>>> If i hide them the scan is ok.
>>>
>>> Any idea whats wrong?
>>>
>>> Regards
>>> Roland
>>>
>>>
>>>
>>>
>>
>>

Meanwhile we have detected that it may be possible
that there is a relationship between the problem and
the operating system.
The wrong view with XbpStatic can reproduced only on some pc.

Roland

"Roland Gentner" <rg@gentner.net> schrieb im Newsbeitrag 
news:135d489a$66683b88$cf88@news.alaska-software.com...
> Hello Joe - alltrim() did not help
>
>
> "Joe Carrick" <joe.carrick@dslextreme.com> schrieb im Newsbeitrag 
> news:15b4d998$4af82211$8291@news.alaska-software.com...
>> Have you tried alltrim() ?
>>
>> On 9/14/2010 1:21 AM, Roland Gentner wrote:
>>> Problem encircled:
>>>
>>> Attached is a screen shot that show the bar code results of using 
>>> XbpStatic
>>> and GraStringAt among each other.
>>> GraStringAt shows the right bar code.
>>> XbpStatic seams to have problems with the space before the first bar.
>>> The space is coming automatically from the bar code font.
>>>
>>> Roland
>>>
>>> "Roland Gentner"<rg@gentner.net>  schrieb im Newsbeitrag
>>> news:6c483b41$5c92b3fc$9131@news.alaska-software.com...
>>>
>>>> Additional Informations:
>>>>
>>>> Some ansi/oem-problems solved
>>>> BUT
>>>> when i use GraStringAt the BarCode is displayed OK,
>>>> when i use XbpStatic the BarCode is wrong
>>>> (see attached pictures).
>>>> The wrong BarCode has three additional bars at beginnig.
>>>> If i hide them the scan is ok.
>>>>
>>>> Any idea whats wrong?
>>>>
>>>> Regards
>>>> Roland
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>
>

Roland Gentner wrote:

> Meanwhile we have detected that it may be possible
> that there is a relationship between the problem and
> the operating system.
> The wrong view with XbpStatic can reproduced only on some pc.

I wonder if there is a difference between the two display methods if you
are using a normal font (=not barcode)?

Thomas

The the problem is only with the bar code font.
With "normal" fonts i havent detected a differency.

Roland

"Thomas Braun" <spam@software-braun.de> schrieb im Newsbeitrag 
news:1bwlx2tnfbczo$.16d483de9d4xr$.dlg@40tude.net...
> Roland Gentner wrote:
>
>> Meanwhile we have detected that it may be possible
>> that there is a relationship between the problem and
>> the operating system.
>> The wrong view with XbpStatic can reproduced only on some pc.
>
> I wonder if there is a difference between the two display methods if you
> are using a normal font (=not barcode)?
>
> Thomas