DHES

Ooooohhh, I liked that.

A Merry Christmas and a safe and happy New Year to all the DHPOS followers.

A great, great reference page for barcodes etc. is http://grandzebu.net/informatique/codbar-en/codbar.htm.

Play with the stuff there.....it's brilliant for making your own in house barcodes too. And is stand alone.

Well, that gave me a lift........

Not that I had anything to post since it stuffed up.....but woooohoooo...yay

Still see visitors here when I drop in for a look. Currently 7 guests and myself here, so I dare say that others are still gleaning information from the forums.

Thanks for that Bruce....really cool to look back at that stuff.

I think I've found a major problem with 7.1a

It doesn't seem to stuff up. Everything I've tried works perfectly.

I just loaded it in and away I went.

Great job Dale and others. Well done.

Thanks Dale. Will wait for 7.1.
As for Bruce, I think his love of the notes is causing a GTC.......Global Tissue Crisis....LOL

Sorry for the delay in replying. Yes using 7.05 on both a XPSP3 and a W98 system. same on both.

Dale, I was testing 26Kg POS today. Entering various transactions and what not. When I went to close the register it crashed with a out of stack space error. I got to the screen where you push #2 to confirm closing and it immediately dumped to this screen. │ CASH SALE: 2419278 15 │ TOTAL PAYOUTS: 0...

I have noticed that when closing the program the printout created is the next transaction number so when I next open it I have a number missing. (well it's not really) E.g. sales for the day number 7564 through to 7925. Closing printout is transaction number 7926. Next sale after opening is number 7...

I also notice when you do an F1 item look up in purchases and then page down you also get A - T on those items, all the way through.

Ahhh, now it's clearer. Yes it is the 16th item in the stock table. I am now making up new labels for this suppliers stock. In EAN13 format!! Something that people who print up their own in-house or manufacturers bar-codes will need to keep in mind if they use code39, code128, or others that allow A...

daleadmin wrote:In every single case the input was 2031093, with no exceptions.

Dale

Just re-read that and noticed that the P was missing. The input should have been P2031093.
Question now is do only some scanners recognise the Alpha characters in Code39? Both the one's I tried here did.