Solved

Cash register reconciliation

Posted on 2013-10-22
2
301 Views
Last Modified: 2013-11-06
I am starting to build a database to reconcile the daily sales at my store.
I am planning on asking questions as I get stumped but before I started I thought that...
If you could recommend some structure (architecturally) for me to base my database on?

I will have "X Tapes" that are quick day reports of sales from start of day to the point of the report, and "Z Tape" that are from start of day to end of day reports and start the process over the next day.
If the Z tape is pulled in the middle of the day it will start anew after report
I am using Microsoft Access 2013
0
Comment
Question by:JevonMartin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 
LVL 58

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 500 total points
ID: 39592722
For the "X" tape, I would simply timestamp the transactions.   You can then pull a report for any date/time range that you wish.

For the "Z" tape, include a batch ID field in the table.  Two ways you can use this:

1. Leave it blank until a close out is performed.   Report any transaction with a blank Batch ID, generate a batch ID, then update the records.

2. Have a current batch ID in a batch table.   Something like:

BatchID
CreatedOn
ClosedOn

ClosedOn being null until you close the batch.   Any new transaction is saved with the current batch ID.   When you want to close out, update the current batch ID with a ClosedOn Date/time, and generate a new batch record.

 Then allow reporting for any batch.

 These are just a couple of ideas and there would be many ways to structure this.   You'd also probably want to allow for multiple registers/terminals as well.

Jim.
0
 
LVL 58
ID: 39592729
Best way to approach this by the way is:

1. Determine every type and kind of report or inquiry that you will want out of the application.   ie.   Transactions by Employee, by register, by product/service, by category, etc.

2. Determine what data you'll need to collect.

3. Start on database design.

  Sounds obvious, but many people really don't give #1 a lot of thought.  Many start at #2, then end up down a dead end because they didn't think about what they wanted to get out first.

 Then #3 and the app often changes drastically.

Jim.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
Traditionally, the method to display pictures in Access forms and reports is to first download them from URLs to a folder, record the path in a table and then let the form or report pull the pictures from that folder. But why not let Windows retr…
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question