>>>>>1- Store the register sales data in local tables on the "cash-register PCs" and read them into the server table as a part of the daily closing process.
>>>>>2- Store the register sales data on the server.
>>>>
>>>>We use an off-the-shelf package that runs on our cash-register PCs, and as apart of the daily closing procedures, the cash-register machine dials into the server and uploads *summary* data to the server. We originally had it set to upload the entire sales detail data, but came to discover the summary data via SQL query was satisfactory for accounting and much more efficient on system resources. HTH
>>>
>>>Roxanne;
>>>Thankyou for your reply. I guess the advantage of keeping the sales information on the cash-regiter pc in your case is "no coding" :)
>>>How flexible is the off-the-shelf package you're using?
>>
>>Flexible? haha... it's one of those "take it or leave it" tools, but it works for us since the server it uploads to is a Unix-based proprietary billing system from a likewise un-flexible service provider.
>
>
>Good to know. Just want to make sure that my mouse trap "is" a new one !! :)

=D) Planning on selling you *new* mousetrap to more than one customer?