Microsoft Access 2002 and Microsoft Access 2003

[matrik02]

My target machine used Microsoft Access 2002 but my development machine used Microsoft Access 2003. How I can update the Microsoft Access 2002 in my target machine?

[si_the_geek]

I'm not sure what you mean.. can you clarify please?

[matrik02]

Like this.. I can related one table to another table in the Microsoft Access 2003 because my development machine used Microsoft Access 2003. It works if I deploy the program to the target machine that have Microsoft Access 2003 installed in the machine.

But If the target machine have Microsoft Access 2002, then I cannot relate one table to another tables after I deploy it.It is a conflict between the ADODB connection because difference version?

[si_the_geek]

ADODB shouldn't care, as long as the files in both cases are .mdb files.

There should only be a difference if you have got a Reference to Microsoft Access Object Library (based on what you have posted, you shouldn't have a reference to it).


If you haven't got a reference to it (or it still doesn't work after removing the reference), post the code that has the problem.

[anhn]

Change Reference to Microsoft ActiveX Data Object x.xx Library to lower version that available on all machines.

[matrik02]

What you mean with Microsoft ActiveX Data Object x.xx Library ? It this line below in my SETUP.LST ? Should I included Microsoft ActiveX Data Object x.xx in the package?

[email protected],$(CommonFilesSys),,$(Shared),11/30/07 4:37:08 PM,81920,2.81.1132.0

[si_the_geek]

No, don't distribute any ADO components, only distribute MDAC as a whole (and only if the target PC's have Windows 2000 or earlier).

If you have actually installed that file (and others for ADO), I strongly suggest you install MDAC (at least version 2.7) on those PC's to undo the damage you have done.


At that point, go back to the project. Check your references and code - as that is where the problem is most likely to be.

[matrik02]

I checked and I used Microsoft ActiveX Data Object 2.7 . So what step I should do so that my relate tables success in both version 2002, 2003


1) If my target machine is already installed with Windows XP services Pack 3. which OS come first? Windows XP or Windows 2000 ?

2) MDAC and Microsoft ActiveX Data Object 2.7 what is difference ?

3) If I distribute MDAC, it is installed automatically when I deploy the package?

4) I heard that people said don't distribute any ADO components. Why you said that? But my program used Microsoft ActiveX Data Object 2.7 so I distribute it, If I not distribute it, I unsure whether my program work or not.

[si_the_geek]

1) 2000 was before XP (which I think was 2002 or 2003). XP comes with MDAC 2.8 (and thus ADO 2.8), so MDAC does not need to be distributed to that.

2 & 4) ADO is part of MDAC, there are other parts too, and they all need to be able to work together - they can't if there are different versions mixed together. If you install just part of MDAC, you may well break the rest of it - and so all of the programs which make use of it.

3) No, you need to run a separate installation.

So what step I should do so that my relate tables success in both version 2002, 2003

Did you happen to notice that I have twice asked about the code?

[matrik02]

Change Reference to Microsoft ActiveX Data Object x.xx Library to lower version that available on all machines.

Why I should used lower version? It is Microsoft Access 2002 and Microsoft Access 2003 used difference Microsoft ActiveX Data Object x.xx ?

[matrik02]

No, don't distribute any ADO components, only distribute MDAC as a whole (and only if the target PC's have Windows 2000 or earlier).

Oh, I still unclear. if i don't distribute any ADO, I think my program can't run because most of my code used ADODB and Microsoft ActiveX Data Object x.xx to connect the Microsoft Access database. It is this Microsoft ActiveX Data Object x.xx as already exist in Windows XP if I deploy the program to Windows XP .

[si_the_geek]

Why I should used lower version? It is Microsoft Access 2002 and Microsoft Access 2003 used difference Microsoft ActiveX Data Object x.xx ?

anhn's suggestion was assuming there were different versions installed on different computers.. if your target computers all have Windows XP (or you install MDAC) then you don't need to do that.

Oh, I still unclear. if i don't distribute any ADO, I think my program can't run because...

Your program needs ADO, so ADO needs to be installed on the computer, but not directly.

If you need to install it, install MDAC. Never install parts of a framework, instead install the whole framework (MDAC). Otherwise you will break things, perhaps even ADO.

You don't need to install MDAC on XP or later, as it is already on there.