BCMS Bill Posting

I forgot when I finished the BILL RANGE feature in the Bill Posting module, but yes, I've already finished it. I think that was last week or the week before.

I might remove the Sequence Number Range frame I've included (not yet functional), but that'll have to wait.

I think I will have to replace the prior button type of the PRINT button in the Ledger module so that the user will not have to click back on the previously used button whenever they changed customers after printing.

San Jose Malino customers

Finally!

I spent almost all day (and all afternoon yesterday preparing for today) in making the meter records for the Malino customers!

Now it will be up to RAJE to find the missing customers/meters.

San Jose Malino take-over

Oh, man!

I've been spending lots of precious time manually matching RAJE's data with PRESCO's. I started this on Friday morning, and passed it on to Rico, who passed it on to their 2 OJT's. Now I'm posting this at home, after a few hours of more manual matching! The OJT's didn't seem to get much work done. :-(

Okay, just to vent out my frustration with RAJE, especially with Mariliz, who should've known better and asked for Account Numbers in the first place:

I used VLOOKUP() functions to search for account numbers in the PRESCO data where the name matches RAJE's. Problem is, Mariliz just typed into the computer whatever RAJE's meter readers wrote by hand, so there were a lot of TYPO's, both in names and serial numbers, hence, a lot of "#N/A" values found. These "N/A's" are the ones we need to scrutinize. Some are simple enough to find, like missing MIDDLE INITIALs. Others are a little tougher, like misspelled surnames and/or first names. A little bit tougher still are those with two first names and/or full names (!).

I also included another VLOOKUP() for the serial number just to verify that the account number found was "legitimate." I had to do this because there were multiple records with the same registered names. Same problem with TYPO's here.

This is the manual matching procedure:

I find the next record with no matching account number (#N/A). I press CTRL-PGDN to go to the PRESCO sheet, press CTRL-F to open the Find dialog box, type in the surname, press ENTER, and if there's a matching surname, i look for the first one with a matching first name. If still not found, I look for a similarly spelled surname, and so on. If the surname search fails, I search for a matching FIRST NAME with a SIMILAR-SOUNDING SURNAME, and this usually is the last step. If still not found, I mark it so.

Here are a few samples of matches I made, after using much effort:

RAJE: Dolante, Dexter.
Dolante not found in PRESCO's data.
Dexter found with surname Dollente. See what I mean?

RAJE: Ignacio, Cynthia
found: Ignacio, Abel / Cynthia. not so hard.

RAJE: Dizon, Angelito.
found 1 Dizon, Angelito, METER doesn't match.
found 2 "Dizon, Angelito / Gertrudes", second one matches Meter serial #. I add "#2" to the name in PRESCO's data, and make a similar change in RAJE's data. Marked.

RAJE: Figueras, Elizabeth.
Figueras not found.
Elizabeth searched, found "Figuerres, Gerald / Elizabeth"

RAJE: Garcia, Maria
found several Garcia's. matching meter serial# is "Garcia, Ma. Blecille"

another FIGUERAS -> Figuerres.

"Binondo, Alvin" -> Binondo, Arvin

"Nario, Salta" -> "Salta, Roda / Mario". serial#39308591 vs. 39308519

"Varba, Percival" -> "Barba, Percibal"

"Dobie, Jude" -> "Doble, Jude"

"Mecedita, Santos" -> "SANTOS, MERCEDITHA B."


THIS ONE'S TOUGH:

"Caplasa, Lee Joy" -> "Gadiaza, Leo Joy"

Let's go on...

"Tubon, Mario Jr. I" -> "Tubon, Mario L. Sr. / Marie"

"Antonio, Ramil" -> "Antonio, Raminer L."


..... and many, many more....

After this, I'll have to make a pivot table to count instances of account numbers, to check for duplicate records...

For now, I think I'll go to sleep.

It's already 11:23 PM, I can feel my pimples popping out. :-(

BCMS User-Friendliness Updates

After the last time I made changes and improvements to BCMS, I've done the following:

1. Fixed the "not unpressed buttons" issue on the Consumer Ledger and Consumption buttons in the Ledger module.

2. Gave access to Disconnection clerk to the overpayment application module because she needs to see which (and how many) months the receivables were for. Initially, she only wanted me to force the Ledger tab in the Ledger module to display the last entry, but I was not able to find a way, at first.

3. In relation to #2, found the way to force the listviews on the Ledger module to ensure that the last item is visible [listview.listitems(listview.listiems.count-1).ensurevisible or some such hocus-pocus].

4. Switched the listviews in the Ledger module not to HIDE the SELECTION highlight when out of focus.

5. Added Syntax-error Prevention code on Bill Posting module when searching for areas.

6. Pressing ENTER on Area field will now erase the contents, if it already has been looked up prior.

7. Added TOTALs to the financial columns in Overpayment module.

8. Switched reports on Rose's new PC to the Epson FX-1170 driver.

BCMS: Overpayment application

Whew! Finally!!! The Overpayment module now takes into account the amount of VAT and UC to apply from bill to bill! Woohoo!!!

In the process, I eliminated some more primitive coding by streamlining again; specifically, using the iif(), min(), and max() functions. The latter 2 I had to build functions for. No big deal.

BCMS: Historical data on consumers

Finally got to finish the Connection History and Meter History tabs in the Consumer Ledger! :-)

BCMS: Additional Feature

Finished the enhancement for the Teller collection report module.

Will now deploy the new .exe for Agnes to witness the last remaining uncorrected VAT discrepancy.