When is True NOT True??? 1

[Soundsmith]

I have a routine in Access 2000 that has worked fine for months, like the following:

    Select Case theForm
    Case theForm = "FrmAddTrans"
        Set rst = Form_frmAddTrans.RecordsetClone
        obal = rst("orig_bal")
    Case theForm = "FrmRecalcAll"
        Set rst = Form_frmRecalcAll.RecordsetClone
        obal = rst("orig_bal")
    Case Else
        Set rst = Form_frmClaims.subPay.Form.RecordsetClone
        obal = Form_frmClaims.orig_Bal
    End Select
[\code]

It has suddenly stopped functioning - I pass it the form name, "frmAddTrans" and it steps past the case selection to the next case.
I have verified the name, and even checked in Immediate:

? theform="FrmAddTrans"
True

yet it continues to skip past the case.

Any ideas? I've tried rebooting to no avail.

Help, please!
 David 'Dasher' Kempton
The Soundsmith
[URL unfurl="true"]http://www.thesoundsmith.com[/URL]

 

[WildHare]

This is very wierd but it works:


Select Case theform
Case Is = "frmAddTrans"
Debug.Print theform
Case Is = "FrmRecalcAll"
Debug.Print theform
Case Else
Debug.Print " no form "
End Select


Your posted code looked fine to me. That's whats odd... Ex-JimAtTheFAA
78.5% of all statistics are made up on the spot.
Another free Access forum:

http://www.forumco.com/jmhare

More Neat Access stuff at

http://www.jmhare.com/wildhare2.htm

 

[WildHare]

Just noticed it also worked like this, with no EQUAL SIGN or IS :

Select Case theform
Case "frmAddTrans"
Debug.Print theform
Case "FrmRecalcAll"
Debug.Print theform
Case Else
Debug.Print " no form " Ex-JimAtTheFAA
78.5% of all statistics are made up on the spot.
Another free Access forum:

http://www.forumco.com/jmhare

More Neat Access stuff at

http://www.jmhare.com/wildhare2.htm

 

[Soundsmith]

Thanks, WildHare. I didn't try tie IS function, but Case "frmAddTrans" worked just fine.

(Of course, CASE theform="frmAddTrans" worked perfectly for six months! Go figgur )
David 'Dasher' Kempton
The Soundsmith

http://www.thesoundsmith.com

 

[WildHare]

Bit decay. Common problem in code that hasn't been varnished with new and improved [red]"ShooBug"[/red].

After a while, acid rain eats away the protective covering of crud and exposes your working code to electron-lossage.

Ex-JimAtTheFAA
78.5% of all statistics are made up on the spot.
Another free Access forum:

http://www.forumco.com/jmhare

More Neat Access stuff at

http://www.jmhare.com/wildhare2.htm