Keeping track of code snippets that need revision 1

[AlanJordan]

This technique is so simple that I hesitate to share it with people, but I use it everyday. Perhaps you'll find it useful.

When I am copying-and-pasting code, I start put a '@ before the block of code and an '@@ after the block of code. Example:

Sub ShowEmployeeNumber()
'Show employee number and ask user to verify it
'@
    Dim db As Database
    Dim qdf As QueryDef
    Dim rs As Recordset
    Dim strQueryName As String
    Dim strNoOfLogInsToday As String
    strQueryName = "qry_p_GetKKEeNumber"
    Set db = CurrentDb()
    Set qdf = db.QueryDefs(strQueryName)
    Dim strKKLogin As String
    Me.cboEEFullName.SetFocus
    qdf.Parameters("Enter Full Name") = Me.cboEEFullName.Text
    mboolNextStepOK = False
'To avoid recordset type mismatch problems, assure DAO is loaded before ADO in references.
    Set rs = qdf.OpenRecordset(dbReadOnly)
    If Not rs.EOF Then
            gstrKKLogin = rs(0)
            gstrFirstName = rs(2)
            gstrLastName = rs(1)
            glngEENum = rs(3) 'KKTempID
            Me.lblKK.Caption = "Your Kids Kottage Login is " & gstrKKLogin
'@@
                'Here is where we do processing
                Me.lblEeNum.Caption = gstrKKLogin
                'Me.lblEeNum.Caption = glngEENum
                With Me.lblKK
                    .Caption = "Please verify your Kids Kottage Login"
                    .ForeColor = OK_GREEN
                End With
                Me.fraVerifyEENum.Visible = True
    Else
                MsgBox "Please tell a supervisor that there is a problem finding your Kids Kottage Login.  You may have to log in manually today.", vbExclamation
                GoTo StopProcessing
    End If

                'Do nothing.
StopProcessing:
    'We have found our record, and recorded the information.
    'Release memory and do housekeeping
    Set rs = Nothing
    Set qdf = Nothing

End Sub

When I am finished revising the code, and it is tested. I remove the comments.

This is particularly useful when I get called away from what I am doing, and I have quickly figure out where to start again.

It's also a handy way to double check code that I have adapted.

 

[PHV]

'To avoid recordset type mismatch problems, assure DAO is loaded before ADO in references
A safest way is to fully qualify your object:
Dim rs As DAO.Recordset

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Zion7]

Thanks Alan,
Clever way to avoid confusion and neglect!

 

[AlanJordan]

To avoid recordset type mismatch problems, assure DAO is loaded before ADO in references
A safest way is to fully qualify your object:
Dim rs As DAO.Recordset

Dear PH,

Thanks for the reminder. I certainly don't need database corruption. I went through and explicitly declared all non-ADODB recordsets as DAO recordsets. I also did the same with Querydefs.

A question, if you don't mind: Is there any advantage to:

Dim db as DAO.Database

Regards,
Alan

 

[RoyVidar]

Perhaps not at the moment ...

... but after you've had a couple of entertaining debugging sessions where you can't figure out the errormessages on objects you've worked with for ages ...

What do you know now, about future object libraries you will need for this project? Or future versions of the object libraries you use now? Could it be a possibility of those containing a Database object different from DAO's?

I'm inclined to believe (and emphasize believe), that fully qualified referencing might give a very tiny performance effect too, as I'm imagining that it doesn't have to look through all of the references for this object, but can "jump" right at the correct library.

Roy-Vidar