Sat Tracker Table reference.
The Sat Tracker product consists of 3 databases:
- SatTracker: contains local tables (e.g. user preferences), forms, queries, reports, and modules (programs).
- SatTrackerData: Contains information such as global preferences and customer, receiver, programming and service data.
- Comm: commission data.
The backbone of the system are the tables in SatTrackerData. Here is a brief description of the most important tables:
- The Customer Table (the Customer Form)
- one record for each customer
- contains information such as customer name and address, and a unique customer ID.
- The Receiver Table (the Receiver Form)
- one record for each receiver
- contains information such as receiver id's, cost
- linked to the Customer table via the Customer ID, and to the OrdersTable via the CustomerId and the OrderDate.
- The Service Table (the Service Form)
- one record for each product or service
- contains information such as the name of the product or service, the cost, and the number of units
- linked to the Customer table via the Customer ID, and to the OrdersTable via the CustomerId and the OrderDate.
- The Program Table (the Program Form)
- one record for each program sold
- contains information such as the name of the program, the cost, and the duration of the service
- linked to the Customer table via the Customer ID, and to the OrdersTable via the CustomerId and the OrderDate.
- The Payments Table (the Payment Form)
- one record for each payment made
- contains information such as the amount of the payment and how the payment was made
- linked to the Customer table via the Customer ID, and to the OrdersTable via the CustomerId and the OrderDate.
- The Orders Table (the Order Form and the Order Summary Form)
- one record for each order created
- contains information such as the salesperson, technicians, and what the customer requested
- linked to the Customer table via the Customer ID.
- Orders may be created implicitly (by entering a receiver, service, payment, or program information with an order date that does not yet exist), or explicitly, by creating a new order. What happens internally is: any time you change information in one of the above tables, SatTracker recalcs order information for the customer. New orders are created for customer/order date pairs that do not yet exist in the orders table, and existing orders without any goods or services, or "service requested" information are deleted. The delete case would occur if you changed the order date on, say, a receiver, and it was the only item in the order.