6014. Did some research on EPPMS, recalling how to run the application in backup mode. On FrontAccounting development, we implemented pay item data entry that involved displaying checkboxes, selecting values from array-based dropdown lists, and amount columns; just about ready to move on to employee data entry.

6025. Visited EPPMS client and set up automatic database backup on a client computer while restoring more database backups for a user and giving the user full access to some 2008 and 2009 backups.

6036. In less than two hours we added two useful features to Randomizer to automate things we’d been using slower methods to achieve the past few weeks, “Simple Top 10” target to show the most recently drawn top 10 numbers by frequency within the past 8 days, and a List Filter button on the Best Couples window to show only couples from a given list of numbers. For FrontAccounting, we began implementing employee data entry and this would take some days as several tables would be involved.

6040. Implemented refund of phone call amounts via Payroll in MoneyBooks Data Manager but only effective at the database level as we didn’t recompile the module yet. Continued building the employee form in FrontAccounting and by day’s end could see the skeleton form displayed in the application, remaining to add up all the necessary columns in the different sections.

6051. In less than 30 minutes we made a database SQL code change in Randomizer that resulted in very significant improvement in the time taken to update the Best Couples List, down to just a few seconds from the over two minutes it used to take, as now only the most recently-entered draws were examined rather than everything. In FrontAccounting we completed setting up the initial employee form and began live testing and debugging.

6062. Troubleshoot the employee data entry form in FrontAccounting, trying to find out why an existing employee record was not being displayed.

6073. Made some progress in the employee form trouble-shooting in FrontAccounting, finding a work-around that got the data displaying, and then testing amending, deleting and cloning (copying) records, but because the image display didn’t work we weren’t satisfied and so set to redoing the form code without using a table class, having seen things working.

6084. Sorted out all problem issues with the employee form in FrontAccounting.

6095. Implemented the range distribution frequency as a target in Randomizer, so we didn’t have to resort to dbisqlc to run some SQL code each time. The main work done in FrontAccounting was creating database objects—triggers and functions—to come to play when the employee and payroll item tables were edited, before moving on to implement the remaining tabs on the employee form, learning about some MySQL limitations (compared to Sybase SQL Anywhere) in the process.

6106. In FrontAccounting, we implemented the Fixed tab on the employee form, for fixed item data entry, and moved on to the Loans tab.

6110. Modified Randomizer to show the number of wins for each frequency distribution range and to sort the list by wins rather than frequency, as the wins was more important: This showed that for the prior 50 numbers drawn, range 4 (31-40) and 6 had the best frequency of 8 with 2 wins each, but for the prior 30 numbers drawn yesterday it was range 4 that kept up at frequency 6 and 2 wins while range 6 wasn’t among the best 4. In FrontAccounting we completed coding of loans data entry and began testing and revising it.

6121. Concluded work on the employee data entry in FrontAccounting after a week and successfully sorted out an issue created along the way that stopped some earlier data entry options from working.

6132. Implemented variable data entry in FrontAccounting and battled with a strange issue that came up, nothing being displayed on the lower form section when the Edit button was clicked against a row in the upper list section, even with no database errors being issued.

6143. After resolving the strange issue with the variables entry form, we were next able to turn to implementing payroll processing.

6154. Implemented the new payroll processing function in FrontAccounting, having to address peculiarities of MySQL’s dialect of SQL in the process.

6165. In FrontAccounting we implemented SQL code for tax calculation and then activated the menu option for calling the new payroll procedure, creating a simple one-page document from scratch for the purpose of getting the pay date and confirming the process; also downloaded tutorial on AJAX from the W3Schools website.

6176. Implemented our first reports in FrontAccounting, starting with a simple employee list to get us started then moving on to the more complex payroll listing and finally ending up with the even more complex payslip report.

6180. Improved on the payslip report format while learning more about the reporting classes that actually did the job, seeing several ancestors for the FrontReport class, and later started work on the payroll posting conversion SQL code.

6191. Implemented payroll posting, end of year processing and defaults setting although yet to test fully and add GL journal generation to the posting.

6202. In FrontAccounting we tested payroll monthly posting without GL journal and then end of year processing, moving on to learning more about FrontAccounting GL journal generation.

6213. In FrontAccounting we implemented GL journal generation for payroll and did necessary testing and revision after supplying GL accounts for deduction items, departments and pay points.

6224. We concluded revision and testing of payroll posting with GL journal in FrontAccounting, and implemented the first and only (for now at least) “inquiry” option, for payroll history. Concluded investigation into non-delivery of ordered item by EMS Nigeria reported by our TripleClicks client. Collected item from EMS after it was recently returned undelivered, advising client on alternative options for receiving item.

6235. We revised the Watch List in Randomizer to ignore draws recorded before a watch was entered.

6246. In FrontAccounting we first made sure switching from regular payroll to graded payroll worked, then we completed the payroll history inquiry implementation, the only thing missing compared to the MoneyBooks Payroll version being the display of totals.

6250. Began real work on the Royalties module for FrontAccounting, reviewing the menu earlier set up, creating the database tables and implementing the first two data entry forms for authors and royalty items.

6261. In FrontAccounting, we implemented the second tab for the authors and royalty forms, both supplying data for the author/royalty table, either items for an author or authors for an item; afterwards we implemented default settings data entry and then due to absence of sales data in the database we’d been working with, we migrated the database objects to a demo database. This turned out a lot more cumbersome than if we’d used SQL Anywhere because foreign key definitions weren’t separated out of table definitions and the tables weren’t placed in the backup file in the same sequential order they were created.

6272. We looked into the issue of foreign keys and restoring backups and saw MySQL’s approach, to turn off the foreign key checks at the top of the backup file and then back on at the end. Researched sales records storage in FrontAccounting and wrote the SQL procedure to get them and calculate royalties for authors by the end of the day.

6283. Tested, revised and concluded royalty calculation in FrontAccounting, implementing our own audit trail logging as well.

6294. In FrontAccounting we implemented royalty inquiry then posting of royalties, enhancing the GL journal creation process while doing so.

6305. Much progress was made on FrontAccounting development as we completed royalty posting, payment data entry and posting, as well as royalty data entry.