Re: Using Access 97 and Access 2003 on same computer

anonymous_at_discussions.microsoft.com
Date: 08/16/04


Date: Mon, 16 Aug 2004 16:56:04 -0700

I installed them in separate directories. Since we use
mostly use Access 97 we had changed the default program
for MDA, MDB, etc. to Access 97.

Thank you for the info. You've encouraged me that I can
get this thing working somehow. I'm going to try
reinstalling Access 2003 and I will see if that helps.

>-----Original Message-----
>When you installed Office 2003 did you install to a
completely separate
>directory than the default or the location of the
Office97/Access97
>database? If not, this is your problem. Uninstall Office
2003, Uninstall 97.
>Reinstall 97 to one directory then install Office 2003 to
a completely
>different directory. Installing Office 2003 to a
completely different drive
>is even better or vice versa with Access 97.
>
>VS.Net 2003 will not interfere to my knowledge with
either application
>version. I have VS.Net/Access 97/Access 2002 running on
my desktop machine
>with no conflicts.
>
>Be aware that if you double click on your Access 97
database it will not
>open Access 97 it will open Access 2003. If you double
click on Access 2003
>and no other database is open it should invoke Access
2003. If you have
>Access 97 open and double click on a 2003 database or 97
database, it will
>open the database under a new instance of Access 97. If
you need to open two
>different versions at any time you have to open both
through Start |
>Programs | Access 97 | Pick the database and Start
|Programs | Access 2003
>|Pick the database. It does not matter which version you
open first.
>--
>G Vaught
>
>"TechniMom" <anonymous@discussions.microsoft.com> wrote
in message
>news:2a2201c47e32$a5ae61b0$a301280a@phx.gbl...
>> Access 2003 gives me a "Microsoft Visual Basic"
>> dialog "Object library not registered". Clicking help
>> gets me Access 2003's help file which says to reregister
>> the application.
>>
>> I have a standalone version of Access 97 that I've been
>> using for years. Last year I installed Office 2003
>> Professional, but kept Access 97 and have been using
>> Access 97 ever since.
>>
>> My husband also has Visual Studio .NET 2003 installed on
>> our computer.
>>
>> Now I want to use Access 2003 for a new database (and
>> VBA), but keep Access 97 for my old ones. (I don't have
>> the time to deal with converting all my VBA code to
2003).
>>
>> If I reregister Access 2003, will it mess with the
>> functionality of Visual Studio or of Access 97?
>
>
>.
>



Relevant Pages

  • How to build a VAX/VMS emulator on Fedora Core 3 Linux
    ... make install the libpcap for ethernet support on VAX emulator ... Is the OpenVMS media ready to be mounted? ... * Do you want to install the MSGHLP database? ... Message from user AUDIT$SERVER on NEWBB ...
    (alt.os.linux.redhat)
  • Re: Need technique to programatically update back end structure / relationships
    ... Yes, that should work, Bob. ... Install the new one. ... > have the user rename the current production database (after taking a ... > final step of the installation process, I would ask the user to execute ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Error: Cannot find a valid Windows XP Embedded database installed
    ... Both the database and tools are Eval or Retail? ... Microsoft Windows XP Embedded Test Team ... Well, in fact it has a network connection, and it's working without any ... if I install everything in the same computer (tools and ...
    (microsoft.public.windowsxp.embedded)
  • Re: DBD::Informix -- Error Installing On Mac OSX
    ... the environment correctly, as long as the module reasonably clearly ... working Informix environment than to test for things that might not be ... use either the sysmaster database or the informix user to install ...
    (comp.databases.informix)
  • Re: User Rights Assignment - not available - Resolved
    ... Then copy the security file from the \windows\repair ... If none of that works I would try an upgrade/repair install ... shows user rights and use the Resource Kit command line tool NTrights to ... This operation may find that this database is corrupt ...
    (microsoft.public.windowsxp.security_admin)