DHES

DHPOS Development Team,

I'm sure you get 3 million of these a day, and have considered most of them, but here are a couple more for your collection (BTW your software is great):

1. Duplicate Receipts; Would be great if you had the option on a per transaction basis, or out of the history to print another receipt. (In case a customer loses a receipt, the printer jams up during a transaction, etc)

2. Sales Tracking by Time

3. Customizable receipt layout (now I'm just getting picky)

Bear in mind that I have no idea how difficult it is to write these features in, I'm simply thinking out loud.

Thanks for a great program!

Doug

Doug,

We may get this 3 million times a day but now and then one comes along that we hadn't heard of or may already exist.

1. Duplicate receipts
As well as setting DHPOS to print a duplicate receipt for a credit sale, you can reprint any receipt in the history file.

To do this, you must first enable reprinting of receipts from POSCONFG - "Sales Recording-Voids". At the bottom of that screen is an option "Reprint transactions", set it to YES.

Then, from the main menu, you access the "Voids" option, and can press the [TAB] key to reprint a transaction.


2. Sales tracking by time
You're going to have to elaborate on this one, I'm not too sure what you're getting at here.


3. Customizable receipt layout
Now this one has been around a long time, if you run a search on the forum, you will find many more replies about this, so I won't go into much detail.

Basically the code Dale would need to write to first of all, design the receipt in DOS would be massive, and then the code to print it would be equally lengthy.

What is also scary is the amount of error handling and data validation that would have to occur to make sure that you, the user are not putting things in the wrong place where they may print off the edge, jam the computer, send an invalid co-ordinate etc.

Imagine a busy line at your store, and DHPOS crashes because one co-ordinate you entered to put the barcode somewhere else was invalid, and you are then unable to print receipts for the remainder of the day.

Jon Simpson was working on a project, but as is obvious it is still not an easy project, even if not being written in QBasic. The code required for breaking down the elements of the receipt and putting them back together in your desired order is not easy. I know, I wrote part of the parser for him to split the plain text receipt into small chunks of data.

The parser must not only break down these pieces, but it must recognise the type of receipt, e.g. sales, return, void, open, close. Otherwise if it tries to parse the wrong format, undesired results could occur.

So in summary - don't hold your breath but there is a small glimmer of hope. In the meantime, DHPOS does more than most DOS POS applications by allowing you to edit the labels on your receipts from the "Receipt Language" feature of POSCONFG.

Thanks for your comments.

Thanks for the reply. I will definitely check out the duplicate receipts. (as you can tell I am still a relatively new user)

As far as the Sales by Time feature goes. It might be nice to be able to pull a report in order to see when the busiest time of the day generally is, and how that changes depending upon different variables.

For Example, we currently have been tracking our sales by the hour and are able to schedule additional staff based upon our results during key times (ie. 12pm - 3pm) as these are our peak hours.

Doug

Doug,

Actually reprinting a receipt is part of the "Voids" feature. Use the "Sale recording - Voids" feature of the POSCONFG.EXE program to turn on receipt reprinting.