We are expanding our service billing capability and have become stuck on a good way to do this. Info can come from any number of computers, but most will be through 2-3 office machines. We currently check for typos, billing overlaps, and other errors. Right now everything goes directly to a master record table and then uses a form to ID a date range to check the selected bills. It works. The question becomes: as we allow more sites to enter their billing info is there a best way to do this with the least likelihood of problems?
1. Send all info directly to a master record table. This makes sure all the data is collected and problems are resolved later. Conflicts should be minimal but are likely as existing data is checked while rows get added. Final checker may not always see the problem. 2. Send data to temporary tables at each computer as it is entered and review the temp for problems, then append it up to the master table. The temporary nature of temp tables means stuff could happen before a temp is appended and data gets lost. At the same time, hopefully, the person entering will see a problem long before the final checker. Final checker still has to check for overlaps and errors in the master table. 3. Looked at regular tables for each computer but that seemed like asking for problems that temp tables solve. Any other methods people use? Tom Frederick Jacksonville, IL
