Compile error - Method or data member not found - (converting from 2003 to 2010)

[essaytee]

I'm in the process of converting an Access 2003 mdb to an Access 2010 (32 bit version). Needless to say, the Access 2003 version (mdb & mde) have been working flawlessly for close to ten years.



I'm trying to convert the 2003 mdb file to Access 2010 32 bit version (accdb) file.

I'm getting compile errors (Method or data member not found). The debug points to the dot operators of recordset objects as being the offending piece of code. Sample code here: Offending error line is pRst_Data.Edit

Function IsLocked(pRst_Data As Recordset, pStr_UserName As String, pStr_MachineName As String) As Boolean
' Purpose: determines if the current record in the recordset is locked,
'          and if so who has it locked
' Returns: True if current record is locked (and sets pStr_UserName and pStr_MachineName
'          to the user with the lock).  False if the record isn't locked.
' From: Building Applications Chapter 12
    
    Dim ErrorString As String
    Dim intMachineNameStart As Integer
    
    IsLocked = False
    On Error GoTo IsLockedError
    pRst_Data.Edit                     'Try to edit the current record in the recordset.
    pRst_Data.MoveNext
    pRst_Data.MovePrevious
    Exit Function               'No error, so return False.


IsLockedError:
    If Err = 3260 Then          'Record is locked -- parse error string.
        ErrorString = Error$
        pStr_UserName = Mid$(ErrorString, 44, InStr(44, ErrorString, "'") - 44)
        intMachineNameStart = InStr(43, ErrorString, " on machine ") + 13
        pStr_MachineName = Mid$(ErrorString, intMachineNameStart, Len(ErrorString) - intMachineNameStart - 1)
        IsLocked = True
    End If
    Exit Function
End Function

The above is just one sample of obviously many that are strewn throughout my application. As mentioned, coding is correct under the 2003 version.

I'm unsure of which references are suppose to be included but here is the list as it stands now (Access 2010 version):

• Visual Basic For Applications
• Microsoft Access 14.0 Object Library
• OLE Automation
• Microsoft Visual Basic for Applications Extensibility 5.3
• Microsoft Office 14.0 Access database engine Object Library

The references included for the Access 2003 version are as follows:

• Visual Basic For Applications
• Microsoft Access 10.0 Object Library
• Microsoft DAO 3.6 Object Library
• OLE Automation
• Microsoft Visual Basic for Applications Exensibility 5.3
• Microsoft ActiveX Data Objects 2.1 Library

I've attempted to include the "Microsoft DAO 3.6 Object Library" into the 2010 version but I'm then hit with a name conflict error.

Any advice or suggestions would be greatly appreciated in order to convert my application.

Steve.

[essaytee]

Further, it appears that if I choose to keep my Access 2003 mdb compatible with Access 2002-2003 (Within Access 2010 32 bit version environment) the database works, all the code works.

Surely though, it is possible to convert 2003 DAO code to 2010 code.

[June7]

Try including:
Microsoft Office 14.0 Object Library
Microsoft ActiveX Data Objects 2.8 Library
Microsoft ActiveX Data Objects Recordset 2.8 Library

Shouldn't have to declare the DAO library.

Think at one time I did have code to pass a recordset object to a procedure by argument but changed it to a public declared object in module header.

Might want to declare the type of recordset - DAO or ADO depending on how you set and use the recordset object. Maybe these will be of interest:
http://allenbrowne.com/ser-29.html
http://allenbrowne.com/func-ado.html

[essaytee]

Try including:
... snip
Microsoft ActiveX Data Objects 2.8 Library
Microsoft ActiveX Data Objects Recordset 2.8 Library

Thanks, this did the trick. I can now compile the code and no errors returning. Probably not out of the woods yet but it's a start with the conversion.

Shouldn't have to declare the DAO library.

Think at one time I did have code to pass a recordset object to a procedure by argument but changed it to a public declared object in module header.

Might want to declare the type of recordset - DAO or ADO depending on how you set and use the recordset object. Maybe these will be of interest:
http://allenbrowne.com/ser-29.html
http://allenbrowne.com/func-ado.html

Interesting information. Seems like a simple global replace should do the trick re - the DAO thing.

Steve.