DHES

BUG FIX
In versions 6.15 to 6.19 "No Sales" were not written to the journal file. This will leave gaps in the sequential transaction numbers in the journal. While "No Sales" do not have any effect on sales, taxes, or anything else it is very important that there be no transaction gaps in your journal file.

This bug was caused by the addition of the “Z” readings to the program. The same code that prints the “Z” readings also prints “No Sales.” No Sales are supposed to be saved to the journal file and “Z” readings are not. Things got switched and in versions 6.15 to 6.19 it was the “Z” readings that were set to the journal file and not No Sales. Not good.

This bug occurs even of you do not track “Z” readings. If you save your journal to a file you really must download POS version 6.20 if you are currently using POS versions 6.15 to 6.19.

Here is the download link...
<center> http://keyhut.com/pos3.htm </center>

Hi Dale,

I've been testing the new version of POS for the last hour or so and it seems to me there is a little problem in it.
On several occasions in the program, a blank screen appears (sometimes blue, sometime cyan, ... depends on when it happens)
The screen only shows ** on the first (or second, one of the two) screen line and and input cursor on the next (seems to me like an INPUT statement, because an "?" appears before the input cursor).
Perhaps a left-over "breakpoint" statement from debugging or so?

It happens, for example when receiving payment:
1. Choose payment type (CASH; CREDIT; ...)
2. Enter amount + ENTER
3. --- THING DESCRIBED ABOVE HAPPENS ---; I press ENTER to proceed beyond the INPUT
4. Program seems to "hang", but is actually very slow
5. Framework of the main screen appears, but text items are missing (1. Purchase, 2. Return, 3. File Maintenance...). This lasts about 10 seconds (didn't actually time it, but it seemed something like that)
6. Sales screen reappears (my register is set to go directly to the next sale)...

Also happens when closing out register (between "do you want to continue" and "reset merchandise data") and, I guess on several other occasions.

Furthermore, the program seems to react very, very slow on some operations (for example in the main menu, waiting time between pressing 1 <enter> (start new sale) and password entry)

I must admit, I have only tested it on 1 machine.


Grtz,


J Mous

J Mous,

I tried it here and it works fine. Probably the problem only occurs when the programs settings are in a particular order and I will have to enter the same settings here to recreate the problems.

There are two things that we could do...
1. Copy every setting on every screen in the POSCONFG.EXE program and post them here so I can manually enter them into the program here.

2. Send me a copy of your ??????.POS file by attaching it to an email and then I will use the settings there to make a trial run. Send it to daleharris@prodigy.net

(Note: replace the ??????? in the file name above with the file name of your register file. For example if, when the program asked you to create a file name for your register, you entered MYFILE then the file you want to send to me would be MYFILE.POS)

I think that you will agree that option #2 will be a lot easier.

Posman sent me a ??????.POS file and the problem seems to be fixed.

It seems as though an earlier compile got zipped up in the distribution file instead of the current version. That was why I could not recreate the problem here because I was using the current file.

So I changed the version number to 6.20a on only the POS.EXE file and uploaded it again.

Download at the usual place...

<center> http://keyhut.com/pos3.htm </center>