Co-Existence of Access 97 and Access 2000

[markhoward]

Hi there,

I know there are issues with having Access 97 and Access 2000 running on the same machine - but could someone tell me the best way to avoid/work around these "difficulties" please.

Thanking yew...

M

 

[LittleSmudge]

Install Office 97 first

THEN install Office 2000 and go through the custom install option and elect to NOT remove O97 as part of the process.

I've never experienced any problems.


What you do have to remember though is that A97 is DAO based and A2k is ADO biased so new code in A2k databases should EXPLICITLY define which is being used in case both library references are active in a specific database

Eg.
Dim rst As Recordset ' Which is what you 'used' to do

become
Dim rst As ADODB.Recordset ' Specifically as ADO

etc..



'ope-that-'elps.



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[RickSpr]

You can install Office 97 after Office 2000 if you temporarily rename C:\Windows (or WINNT)\Fonts\hatten.ttf to another name before you install. If you fail to do this when installing Access 97 after Access 2000, Access 97 will give you an error message that you don't have a license to use it. See the Microsoft Knowledge Base article

http://support.microsoft.com/default.aspx?scid=kb;en-us;241141

for more information.

Also, be aware that whichever version you last opened becomes associated with .MDB and other extensions. If you double-click an .mdb file, you may sometimes get either an "Unrecognized database format" message or a dialog box offering to convert the database to Access 2000. I keep shortcuts to both versions of msaccess.exe in my Quick Launch bar to make it easy to switch. (I also keep shortcuts to both versions of wrkgadm.exe, the Workgroup Administrator.)

One more thing: when setting References in Access 97 to other Office 97 libraries, the Office 2000 DLLs "cloak" the Office 97 ones. For instance, to use the Office Command Bar Object Model, you need the MSO97.DLL library, but when you click the Browse button in the References dialog, it doesn't appear in the Explorer-provided Add Reference dialog. You need to either know where it is or find it in a separate Explorer folder window, then enter the path in the Add Reference dialog.

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein

 

[Bullschmidt]

If you ever install Access 97/Office 97 onto a machine that also has Office 2000 on it, be sure to install Access 97/Office to a different directory than Office 2000. So for example perhaps DO NOT take the default directory of C:\Program Files\Microsoft Office to install things into but instead perhaps change it to something else like C:\Microsoft Office or C:\Program Files\Microsoft Office 97.

And if you use Word mail merge from the database, perhaps install Word 97 too - this is especially true if many users are sharing the same frontend so that one user that would have otherwise been without Word 97 doesn't use the database and have the database change the Tools | References to use a later object model of Word than Word 97.


Best regards,
J. Paul Schmidt, Freelance ASP Web Developer

http://www.Bullschmidt.com

ASP Design Tips, ASP Web Database Demo, Free ASP Bar Chart Tool...

 

[ArkM]

My advice: beware of 97/2000 co-existence. I have mixed 97/2000 links in context menues, Office 2000 troubles after Office 97 components calls, libraries conflicts etc.
We installed Office 97 in the separate loading disk partition with separate OS on all developers PCs. May be it's over-security but it's working fine (for developers only, not for users).

 

[lgbatdw]

LittleSmudge:

you said:

"What you do have to remember though is that A97 is DAO based and A2k is ADO biased so new code in A2k databases should EXPLICITLY define which is being used in case both library references are active in a specific database"

How do I do this?

Thanks in advance

Linda in MN

 

[PHV]

You simply have to qualify ambiguous objects:
Dim rs1 As DAO.Recordset, rs2 As ADODB.Recordset
Dim fldA As ADODB.Field, fldB As DAO.Field
...

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

 

[LittleSmudge]

Thanks for that PHV


Isn't it nice ( and refreshing ) to see people using the Search tool successfully to look up old issues rather than start a new thread on an old subject.

( Congratulations lgbatdw for getting the 'search' to work for you. I normally find out the keywords that I needed for the search when PHV points out the answers and provides the link ! )



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.