Entered wrong closing amount

Isn't the lack of this ability a terrible shortcoming. Any add-ins or otherwise easy solution for this? A list of SQL statements to correct it?

This happens far too often and I have to relearn the procedure and run SQL statements to correct.

"Teri K" wrote:

We switched to running an X report first, checking for errors and then running the Z report.

The X report allows you to change closing amounts before actually zing out he register. It has helped tremendously with removing errors on the closing process. We even established a dollar amount under each cashier to allow for discrepancies.

Jason,

I'm a Microsoft Dynamics VAR but new to POS - do you know where I can get those SQL statements?

Teri

"Jas> Isn't the lack of this ability a terrible shortcoming. Any add-ins or

That's the problem - I need to reinvent the wheel every time I have this problem. I guess I should have written them down...

Of course, we always run an X report first, but that doesn't completely eliminate errors (like forgetting to actually LOOK at the X report or running a Z by accident).

There should be a CTRL-Z :)

"Teri K" wrote:

Is there a way to re-enter the closing amount if you accidently put too many zero's in it and didn't notice until you ran the Z Report?

I have a client who has several closing amount errors they'd like to fix.

Thanks!

change. There are no spaces in those words!

Search for the thread: "SQL to change closing totals"

This is only part of the battle. You have to change the TenderEntry table also.

"Jeff" wrote:

Search for the thread: "SQL to change closing totals"

This is only part of the battle. You have to change the TenderEntry table also.

"Jeff" wrote: > Identify the internal Register ID number > > SELECT * FROM Register > > Find the ID number of the register you have a problem with in the ID column. > > > Backup First!! > > Next, update the info; > > UPDATE Batch > SET [FIELD] = $$.$$ > WHERE RegisterID = reg# > AND BatchNumber = batch# > Thanks!

You guys are great! Thanks for helping me out. I haven't been to the client site you to test this but I'll be there on Wednesday.

Thanks again!

Teri

"Jeff" wrote:

the numbers got there.

It has become such a problem at my stores that I created an Excel sheet that does it all using VBA code. It's not elegant, but it works.

I just wish there was a safe and easy way to modify any RMS table in a spreadsheet format. That would be an add-in I would buy...

Until now I have been using a linked table sometimes in MS Access. It works great, and I have never had any corruption problems, but I always make sure to backup first and never attempt it during business hours.

Dear Teri

Here is the query to set the status to "Blind Closed".

Update Batch Set Status = 8 Where BatchNumber = 12345

Please replace 12345 with the batch number required.

Once you have it set as a blind close you can go back in manager and reset the total to what they should be. Like always before you run any sql command into a live database you may want to do a backup.

Wow. This sounds like a great solution. I suppose it only works for the current (last) batch that was closed, however. Is that correct?

"Afsh> Dear Teri

Dear Teri

Here is the query to set the status to "Blind Closed".

Update Batch Set Status = 8 Where BatchNumber = 12345

Please replace 12345 with the batch number required.

Once you have it set as a blind close you can go back in manager and reset the total to what they should be. Like always before you run any sql command into a live database you may want to do a backup.

Wow. This sounds like a great solution. I suppose it only works for the current (last) batch that was closed, however. Is that correct?

"Afsh > Dear Teri > > Here is the query to set the status to "Blind Closed". > > Update Batch Set Status = 8 Where BatchNumber = 12345 > > Please replace 12345 with the batch number required. > > Once you have it set as a blind close you can go back in manager and reset > the total to what they should be. Like always before you run any sql > command into a live database you may want to do a backup. > > Afshin Alikhani - [ snipped-for-privacy@retailrealm.co.uk ] > CEO - Retail Realm