Meeting with Bryan to look over a test or scratch file to test or play with the data. This is for some changes to the QuickBooks API connections. We have to grab invoice data by date, by corporation, and whether or not the invoices were fully paid or on account. We also needed to track payments and which payments were added after the fact for the on account stuff (accounts receivable).

Switched to a request for an oil, lube, and filter software tie-in. Basically, a one-to-many for customers with one or more vehicles. Went over some requirements and ideas. They need a reverse look-up based on vin number (car or auto id) to customer. They also need a full inventory control system, POS (point of sale) system, payment integration, and preset products and services. We already have a ton of those pieces. We just need to alter the flow a bit. We want to do the same thing with puppy stuff. The big difference is a one-to-many between customers and pets vs customers and vehicles. The whole deal is a multi-relational database with smooth interactions between the different pieces.

Client meeting with an outside developer. He had a number of valid questions about the adilas API sockets. How to turn things on/off, what servers, what corp key id's to use, what API methods, how to check for data, and other settings. They wanted more helps with full location names (not just the location initials), they wanted the additional notes per stock/unit, and they wanted more help on images. They wanted us to build out the full image path for each stock/unit. I told him that I would work on those changes. All valid requests. Good stuff!