Just a followup on SQL Delta. Hopefully this real life story of how I use SQL Delta will help you.
I was tasked to create an application that imports unposted AP transactions into Progression. My gut reaction was that this updates 3 tables, APCTLFIL (last voucher #) and of course APTRXFIL and APTRXDST.
However, these transaction are all subject to 1099s, something I do not usually work with and do not have setup in any of my Macola databases. So I thought it would be prudent to see if any other tables are affected when you process a 1099 AP voucher.
So I took a copy of my database. I then changed one vendor to be subject to 1099s, and entered one AP voucher for that vendor. Finally I ran SQL Delta against the 2 databases, choosing compare structures and compare data.
No structure differences, as expected. I had 2 tables with different data: APVENFIL (the vendor I changed to a 1099 vendor) and APCTLFIL (updated for next voucher #). So this was normal.
The AP Vendor Audit file (APVENADT) had new data (more records) for my modified vendor, a B before change record and a C after change record. Again this was expected.
The APTRXFIL and APTRXDST had new data for my 1099 voucher. I could see by field comparisons that the only difference between a 1099 voucher and a non 1099 voucher was the ap_1099_fg field, which was set to Y and N, respectively.
No other tables were affected. I can now confidently build my application to import AP transactions.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry