For PayRange the new owner gets all the devices, so he will have a list of all devices we own along with where those devices are (DeviceID and MachineID association). He does not get any of the device history (sale or refund data).
We do track all the service history on a machine via the...
Hi,
In tblPayRange the DeviceID is the PK, it's a unique serial number.
In tblPayRangeAssignment I have an auto-number PK that I use when I assign a DeviceID and MachineID based on dates.
Are you saying I should add a different PK in the main tblPayRange?
The current owner identified machines by name only, examples here of what I walked into:
AGT Drinks
AGT Candy
Northloop Office Changer
Northloop Office Pop
Northloop Office Candy
Northloop 361 Pop
Northloop 361 Candy
Smith Building 3rd Floor Pop
Smith Building 2nd Floor Pop
Smith Building 1st...
Thank you, Larry, I'll take a look at this. I appreciate everyone's help trying to get this cleaned up so we can move forward with a cleaner/normalized database.
Hi Mike,
Yes, every time we buy a new batch of devices (10 to a box) we record the device information into a table, tblPayRange. Then when we add the device to a vending machine we add the information to tblPayRangeAssignment and it's associated with a MachineID.
It just happened today. Device...
It's a code that's on each device. We need that PIN to make changes remotely. So the PayRange Device ID (Serial #) and the PIN are two things we have to track. It's typically a 4 to 5 digit code we have to enter.
Yes, we track a lot of information about each individual machine. The machines do have serial numbers, currently the owner does not track that, so I use the InventoryID to track the machines. The new owner may want to use a serial number, so I'll have to add that field to the Machine Inventory...
No, they go all over the place. I have a table where I track the machine's placement/location.
Examples of ones we have:
Laundry Room - 2nd floor
Clubhouse outside the fitness center
Main Entrance, Under Stairs
Employee break room 3rd floor
Garage Lobby level 2
Garage Lobby level 6
Luxor Room...
Thank you. I'm trying really hard to wrap my head around cleaning this up and normalizing the tables before a new owner takes over.
When the original database started it was because the owner had 90% of the info in his head or on paper. He used Excel to track some few things but overall, it was...
It's a device that sits inside of a vending machine to allow for cashless payments. We need the assignment table because the device can be moved from one machine to another. Example, if a machine is removed from one property we can install it at another location. I need to track where the device...
No, we only care about the repair.
Examples:
Machine ID 19: 8/20, Tech Jon, Coin jammed in bottom of coin mech, cleared, fixed and gave refund.
Machine ID 698: 8/16, Tech Joe, Paper and other debris shoved inside coin mech, cleared, up and running.
Yes, while it would be easier to give him the working database, that's not part of the sale, he only gets some of the data as written into the purchase agreement.
What I posted was the start of the tables in a new database. I have to start moving data into those tables that he's allowed to have.
Sorry for the confusion.
We have an Access Database. The company is being sold, the new owner is only getting some of the data. I have to move specific data over to a new database for the new owner. In my creating the new vending database I'm trying to cleanup/fix some of the old tables I have...
We are a vending company. We own and operate vending machines. The database tracks the vending machines that we are the "full-service" vending company for, so we fill them, collect the money, and have revenue share (commission) with some of the properties or management companies we work with...