7034. We revised the account statement generation SQL code in MoneyBooks General Ledger, to order the lines in the same order they were entered each day, rather than in credit amount order. We revised the copying of GL transactions that were outside the current financial period so that those with multiple debits but one credit (or multiple credits but one debit) could be copied as several batch transactions, ending the previous situation where such could not be copied at all.
7045. Work continued on the new Estimating Assistant software, with the creation of a new icon for it and editing of a couple of images for the help file. In the process we saw that Ctrl+Shift+F allowed for multi-file search and replace in Sublime Text editor and this came handy, like replacing all occurrences of “Printwiser” with “Estimating Assistant” in all help text files. New images were later created for the help documentation while existing ones (screenshots) that only needed the icon to be changed were edited. After Estimating Assistant program source was compiled, some program errors were encountered and these were resolved. In the next few days, noted issues with the flexible estimate spreadsheet feature were resolved and the executable file was rebuilt. Unlike Printwiser that has three other modules along with Estimating, Estimating Assistant handles only estimating functions. So it will be a less expensive alternative to Printwiser.
7060. We began v3.52 revision of MoneyBooks GL by implementing copy for the Batch Transaction Form and also creating tables for recording actual cash amounts on a given day rather than the spreadsheet we’d been using for years.
7071. Work on implementing the Petty Cash Actual List in MoneyBooks GL v3.52 continued, including record copying the following day. The following week, we did the first 2025 build of MoneyBooks Payroll as v2.29 to reflect the system-wide Default Date option introduced September 2024. This was followed also by the first 2025 build of MoneyBooks Accounts Payable as v1.50 that also had the Payment Request Form reviewed. We implemented the v3.57 revision of MoneyBooks Data Manager and built the executable, with the following new features: Storing of the phone call amount as well as the call rate (to end rounding issues), adjusting the SQL Query Processor form to make it easier to type multi-line code and providing call copying on the Phone Call Form.
7126. In connection with map editing work being done on Google Maps, we set up a simple tool on our website to report current GPS location coordinate numbers. The coordinates are degree values for latitude and longitude. (Latitude is a measure of the (angular) distance north or south of the equator, while longitude is the distance east or west of Greenwich meridian.)
7200. The first 2025 review of MoneyBooks Sales v2.2 started few days earlier was completed. It includes a new optional multi-addressing feature for invoices, allowing customizing the company address for an invoice.
7270. We set up the SQL Anywhere 11 network database server Windows services for several MoneyBooks databases on a laptop, adjusting the ODBC settings accordingly. This time we used the commandline dbsvc utility rather than going through the GUI, SQL Central, which brought to light the fact that while dbsvc can be used to start a service it created, to start such with the Windows net command, SQLANYs_ must be prefixed to the service name.
A client reported their website was no longer working and we investigated. It was indeed displaying error 404 - File not found rather than coming up. The issue was later traced to a corrupted .htaccess file by the ISP and resolved by the following day.
7281. We had assumed some days before that the issue of inability to update the Rewardical List in Gerian was from using dbeng11.exe (personal database server) rather than dbsrv11.exe (network database server), since on the computer that had the network database server engine running the issue didn’t exist. (An attempt to update after making a change would produce row updated by another user error.) Today we noticed the issue happen again after the network server was installed, and then saw it was because the autoincrement values were not automatically returned to the datawindow object after being assigned to new rows. This was something we corrected in the past and later we recalled the fix and implemented it, replacing the pbodb80.ini that came with PowerBuilder 8 now being referenced with the one we customized about ten years ago to cater for the SQL Anywhere 11 database driver.
7303. Following a request received, we researched free online voting systems, spending most of the time with SurveyMonkey where we set up a sample voting form. We later considered setting up our own programmed form where we will be able to effect better checks and controls, like ensuring each vote is cast by a qualified voter. After reviewing the sample voting form, it was tested on both laptop and Android phone.