Test converting this db to Access 2003

[ghudson]

Do you have Access 2003? If so, can you help me test the conversion of this file from Access 97 to Access 2003?

I need to know what really happens when you convert an old Access 97 db to Access 2003 and the db has the old wizard codes that used the outdated DoCmd.DoMenuItem commands.

• Does the wizard code [DoCmd.DoMenuItem commands] in this form error when converting this db to Access 2003?
• Does Access 2003 successfully convert the code?
• Does Access 2003 leave the old code as-is and error if you try to use the command buttons [or compile the form module]?

Please post back and let me know the results of your conversion.

Thanks in advance for your help!

 

[a.sinatra]

I'll do it when i get home; still at school. Be home in roughly an 1hr 15min.
________
Ferrari F1-2000 Specifications

 

[ifstar]

It converted to both 2000 and 2002 for me.
Guessing 2003 would be fine too.

 

[ghudson]

It converted to both 2000 and 2002 for me.

Thanks for testing for me.

Do the two command buttons still work?

Did Access 2000/2002 convert the code or is it still in the original state using the old Access 97 DoCmd.DoMenuItem commands?

 

[a.sinatra]

Alright, there is no difference between 2000 and 2003, they are one of the same.

The code doesnt not convert, but stays the same and still works.

I used the wizard to make a delete button in 2003, and it still used...

    DoCmd.DoMenuItem acFormBar, acEditMenu, 8, , acMenuVer70
    DoCmd.DoMenuItem acFormBar, acEditMenu, 6, , acMenuVer70

But no difference.
________
BUY SCALE

 

[ghudson]

Thanks Pat and a.sinatra!

I have found it easier to actually go back to the A97 db and fix the errors.

I do not use the DoCmd.DoMenuItem command but all of the novices in our company use the Access 97 wizard so we will have a lot of converting to do when the time comes.

I am trying to get a heads up on potential problems before I upgrade [in about six months] from Access 97 to Access 2003. I have read so many posts that newer versions of Access do not support the DoCmd.DoMenuItem commands after Access 97 yet that does not appear to be true since a.sinatra states that the wizard in Access 2003 still uses the DoCmd.DoMenuItem commands.

Does anybody have any advice [specifics] on what problems to expect when I do upgrade from Access 97 to Access 2003? I do use Access security and install the runtime of Access. I know that I will have to work out my DOA stuff for ADO or keeps the references to DOA.

Thanks!

 

[Rich]

Do MenuItem was supposedly obsolete in 97, it's just that certain depts. in Microsoft don't talk to each other anymore so the wizard dept. hasn't been informed of the change yet, something to do with inter dept. jealousy I think

 

[Mile-O]

ghudson, does this help a little bit:

Public Function UpdateDeleteRecord() As Boolean
 
    On Error GoTo Err_UpdateDeleteRecord

    Dim lngCounterA As Long, lngCounterB As Long
    Dim modModule As Module

    For lngCounterA = 0 To Modules.Count - 1
        Set modModule = Modules.Item(lngCounterA)
        With modModule
            For lngCounterB = 1 To .CountOfLines
                If Trim(.Lines(lngCounterB, 1)) = "DoCmd.DoMenuItem acFormBar, acEditMenu, 8, , acMenuVer70" Then
                    If Trim(.Lines(lngCounterB + 1, 1)) = "DoCmd.DoMenuItem acFormBar, acEditMenu, 6, , acMenuVer70" Then
                        .ReplaceLine lngCounterB, "    DoCmd.RunCommand acCmdDeleteRecord"
                        .ReplaceLine lngCounterB + 1, ""
                    End If
                End If
            Next lngCounterB
        End With
    Next lngCounterA

    UpdateDeleteRecord = True
    
Exit_UpdateDeleteRecord:
    Set modModule = Nothing
    Exit Function
    
Err_UpdateDeleteRecord:
    UpdateDeleteRecord = False
    Resume Exit_UpdateDeleteRecord
    
End Function