DHES

Progress... but now new issues. The dates are printing and recording fine, but now we have a couple new misfeatures that are a little more lethal: 1. Time stamps are not recording. When the user does the cntl-insert bit, the screen behavior shows the status change (green highlight to red highlight),...

daleadmin wrote:You do know that nobody was actually supposed to use the time clock feature?

I tried so hard to avoid it, but the employees kept punching in...

dave

Just want to throw my "Yeah, me too" comment in on this topic. Just printed two weeks of time cards and they all display this week's dates. And, just because I'm picking nits...when you attempt to print time cards using the "print all cards with data" option, you actually get EVERY potential time ca...

Thanks. I thought I couldn't be the first to notice that bug, but didn't find any reference to it either. Probably should have looked deeper.

In any event, thank you for the link.

Dave

I tried using 7.02 on a network with three registers running. Program was running in a window in Vista on each. Time clock worked fine. But, when making a sale, the program crashed every time the sale completed. Ring up sale, subtotal, collect payment, cash drawer opens, and program hangs. The small...

I experienced a 'misfeature' in the employee reports. Instead of printing one report for each employee who had sales/transaction data in their 'file,' I got about 30 reports, one for each 'place holder' in the employee list. I had two employees work that day, have a total of 9 employees set up in th...

bob5731 wrote:How do I setup on a mac?

1. Go buy a copy of Parallels;
2. RTFM

It's so easy a caveman can do it.

We don't accept pure returns either, but will do "even" exchanges for customers for a couple weeks after the sale. We manage it like this: 1. Return the item to inventory through the "Return" function in POS, but change the price to "zero" before subtotal and closing the transaction. 2. "Purchase" a...

The source of my concern is NOT that it takes two screens, while annoying, I can certainly live with that and have been for a couple years now. My concern is that paper gets lost, and I would like the reference data on the return screen in the absence of paper. If a customer doesn't exchange all the...

Since it's been established that an Exchange (a return and a sale on the same screen) isn't going to happen in this lifetime, could we get maybe a pop-up kind of dialog box on the return screen that asks the sales clerk to enter the transaction number from the original receipt? It would help with an...

Item #1: Ability to make an exchange on a single screen, instead of the current "return and then sell" process that now exists. Item #2: Ability for the "Employee Sales" report to function much like the current Total Sales report, e.g., specify a date or date range for which to search for an employe...

Thanks Dale!

dave

In editions prior to 6.2X (the OLD sales screen), when reviewing previous transactions with the VOID feature, the employee name was shown on the screen (Nice to know who screwed up the till sometimes), but on the new screen (in the void area) it's not included. Any chance of getting it back?

When the staff closed the register tonight everything went smoothly with 6.28c. No file writing errors, and the merch data was reset properly. I won't know until morning if the journal file was actually created in a readable format or not, but at least the basic behavior of closing the register and ...

I installed the patch today and will update later tonight when the stores close with how the process went. In examining the journal file angle however, I noticed something different between 6.26 and 6.28. The journal files are now being saved with .A** file extensions instead of .D** extensions. Sim...