Converting Access 2002 to 2000 2

[Knicks]

Does anyone know of anything in particular that would be causing conversion issues from 2002 to 2000. It seems to be centered around opening of reports. I have checked that DAO 3.6 is set higher than Active X. We do not use the open args command.

I do not believe it to be a reference but have not ruled it out. Could it be a DLL or an update issue.

Any help would be appreciated!

 

[PHV]

conversion issues from 2002 to 2000
Which issues ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[Knicks]

The converted database (from 2002 to 2000) has issues with opening reports via command buttons. Even if you create new command buttons afterwards, it still won't open up.

 

[lespaul]

are you really going DOWN....from 2002 BACK to 2000?

Leslie

Have you met Hardy Heron?

 

[Knicks]

Yes.

Unfortunately we have a database that other institutions use but don't have the same version of Access. So whenever we update our database we need to convert it down to 2000 for the other institutions.

 

[genomon]

A good way might be to create a new database in 2000 format on the 2002 machine and start from scratch, or copy any code into a text editor & paste into the 2000 mdb (not import).

"Don't be irreplaceable. If you can't be replaced, you can't be promoted."

 

[Knicks]

The error messages upon trying to open the reports are:

You cancelled the previous operation

and

The open report command was cancelled.

 

[genomon]

So is the code behind the command button something simple, like DoCmd.OpenReport rptname, or is there other code along with it? Why not post it back here if it's complex?

"Don't be irreplaceable. If you can't be replaced, you can't be promoted."

 

[Knicks]

Here is the code from Access 2002 (works in 2002)

Private Sub Command29_Click()
On Error GoTo Err_Command29_Click

Dim stDocName As String

stDocName = "rptNotify"
DoCmd.OpenReport stDocName, acPreview

Exit_Command29_Click:
Exit Sub

Err_Command29_Click:
MsgBox Err.Description
Resume Exit_Command29_Click

End Sub



That code won't work in the 2000 version. Oddly, the code works fine as a 2000 database opened up in the 2002 version.

 

[genomon]

Sorry gotta fly for now - I'll try & reproduce this tomorrow AM (CDST). So far the code works fine when pasted into 2k & 2k2. I'll try & downsize tomorrow. Pretty weird, as the code doesn't get much simpler.
P.S. Try naming controls something meaningful, like "cmdPreview". The folks that follow you and maintain your code will be way happier and less likely to curse your memory.

"Don't be irreplaceable. If you can't be replaced, you can't be promoted."

 

[JoeAtWork]

Oddly, the code works fine as a 2000 database opened up in the 2002 version.

That makes me think it's a references issue.

 

[Knicks]

Here is the reference list for 2000:

Visual Basic for Applications
Microsoft Access 9.0 Object Library
Microsoft DAO 3.6 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library


Here is the reference list for 2002:

Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.1 Library
Microsoft Office XP Web Components


In the orders listed.
Thanx!~!

 

[JoeAtWork]

So it looks like "Microsoft Office XP Web Components" is the culprit. Do you know if you actually need it? If you don't, I would get rid of it in the 2002 version.

 

[genomon]

OK knicks - here is what I did, and my report opens fine:
Created a form & report in Access 2k2 using Access 2k as default file format.
Imported into Acc 2k.
Clicked the command button, & opened the report in acPreview.
The following are the only references set in the Acc 2k installation:
Visual Basic For Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library

My 2k2 references are the same as yours, except I have ActiveX 2.5, and no DAO ref.

I'm pretty sure my little mdb could do without the last two 2k refs and still open a report.

Couldn't reproduce your problem here, so I have to agree with Joe that you should try deleting unneeded references and see what happens.
If that doesn't work, start developing on a 2k machine, or have your stingy clients upgrade to a product that was actually manufactured in this century (you may want to put it a bit more diplomatically).
Good Luck!



"Don't be irreplaceable. If you can't be replaced, you can't be promoted."

 

[Knicks]

Removing the Microsoft Office XP Web Components seemed to have helped - it converted quicker. It still was dead in the water (form, report buttons did not work) but when I created a blank 2000 db and imported the converted db into it, everything worked fine once I added DAO 3.6 reference back (why it got dropped is a mystery?)

Not the smoothest technique but works. Yes, I would say they are being cheap but its a gov't entity - so saving tax dollars! Urrrrrgghh!