Match not functioning for hashtable keys

Question

Updated
Hello,
I'm seeing unexpected behavior and am hoping for a little help.
My PS ver is:
Major  Minor  Build  Revision
3      8      0      129 
Here is a snip that illustrates the issue (reproducible)
$aRecords = $null; $aRecords = @{}
$aRecords.add('tblARecords_1_txtHost','1.1.1.2')
$aRecords.add('tblARecords_0_txtHost','1.1.1.1')
$aRecords.add('tblARecords_1_txtPointsto','1.1.1.2')
$aRecords.add('tblARecords_0_txtPointsto','1.1.1.1')
$gdRecords = $null; $gdRecords = @{}
$gdRecords['typeA'] = $aRecords
$records = $null;$records = @()
$records = 'tblARecords_0'
foreach($g in $gdRecords.Keys) {
foreach($d in $gdRecords[$g]) {
if($d.Keys -match $records) {
write $d
$records = tblARecords_0
But the results i get back are 
tblARecords_1_txtHost
tblARecords_0_txtHost
tblARecords_1_txtPointsto
tblARecords_0_txtPointsto
Even if i substitute the the variablw $wr with the string itself ('tblARecords_0'). It still produces the same same results
Any help would be appreciated

Answer 1

I understand that he is devoting his own time and effort, and that he is not a MSFT employee. For that i am appreciative. My issue is that an approved moderator should be a bit more thoughtful with his language. Normally i wouldn't care but am having one
of those days. Problem is someone may be put off from that approach and may not come back. Perhaps also move on to something else as a result.
I also agree with his request, I probably should have made a reproducible script prior to posting and am updating my question.
Sorry but I disagree.  I know you believe your post is useful and explains everything.  It doesn't.  None of us can decode your variables or comments because we do not have your environment or the full script.
Bill was trying to point put that you need to put in more effort to ensure those who are trying to help you do not have to play guessing games.
Items 7 and 8 are exactly to the point.  Addres those issues and you will likley get a quick and correct answer.
Here are items 7 and 8:
7. Let someone else devise a repro case. When the button click handler isn't called in your sample, by no means should you try to create a smaller repro case. All you know is that your sample doesn't run.
8. Post a sample that depends on a resource you don't describe. Be sure your sample reads from your production database. Don't worry, people will figure out your schema.
¯\_(ツ)_/¯