Re: 2003 to 97
From: Lynn Trapp (ltrappNoSpam_at_ltcomputerdesigns.com)
Date: Thu, 29 Apr 2021 16:33:26 -0500
You can have both A97 and A2003 installed on the same computer. Make sure
A97 is installed first and install A2003 in a different folder on your hard
-- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm "Katherine" <email@example.com> wrote in message news:firstname.lastname@example.org... Amy, I have a similar question. I have several Access 97 databases located on a shared drive. I haven't split the databases into FE and BE yet, but when I do both will be located on the server (rather than placing the FE on each users desktop). We are all currently using Access 97 but are being upgraded to Access 2003. As our regional offices are located throughout my state, this will be a long process. My office is scheduled for mid July. Other offices are scheduled as early as May and as late as October. Am I correct in understanding that I will need to be set up with two computers - one running Access 97 and another running Access 2003 - during this process? Won't I need 2003 running to convert the 97 version and 97 running to maintain the BE until every office gets upgraded? Would I be wise to make a plea to my department's management team to provide me with two computers? Thank you Amy for any advice you can offer. >-----Original Message----- >Hi Kelly, > >My name is Amy Vargo. Thank you for using the Microsoft Access Newsgroups. > You can convert an Access 2002/2003 database to 97 format. To do so, open >your database in Access 2003. Go to the menu bar and choose Tools, >Database Utilities, Convert Database, to Access 97 File Format. You cannot >directly open an Access 97 database in Access 2003. You must convert it, >and vice versa. You cannot open an Access 2003 database in Access 97. >Another option would be to split the database. You can create an Access 97 >backend file that contains the tables and use different 97 and 2003 >databases as frontends that are linked to the tables in the backend, but of >course each having it's own other local objects. This way users with >multiple versions of Access can still share the same data. > >I hope this helps! If you have additional questions on this topic, please >respond back to this posting. > > >Regards, > >Amy Vargo >Microsoft Access Engineer > > >This posting is provided 'AS IS' with no warranties, and confers no rights. >You assume all risk for your use. © 2001 Microsoft Corporation. All rights >reserved. > > >. >
- Right-menu turns white and Access stops responding
... Recently we upgraded several of our computers from Windows NT to Windows XP. ...
We have an Access 2000 database. ... The back-end resides on a SBS 2003 server.
... it is also happening on one running Access 2002. ... (microsoft.public.access.forms)
- 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 ... >>> case
the back-end database is left alone and eveything else is ... (microsoft.public.access.tablesdbdesign)
- Re: DAO360.DLL - can I redistribute it?
... Your point about the only real advantage of ADO being its ability to ... My
big worry about telling them to install MDAC is that when it installs the ... If the database
is Jet/DAO, you'll still need Jet on the target ... (microsoft.public.access.developers.toolkitode)
- Re: A few good beta testers wanted
... My apologies, Graham. ... > providing peer-to-peer assistance on Microsoft
products and services. ... >> Install: C. ... >> To database
will be flagged A, Tables which exist in the To ... (microsoft.public.access.modulesdaovba)
- Re: SP2 installation hung
... Okay, here's the follow-on. ... I got the same "SP2 did not complete"
... installer can communicate with some database that way? ... >> proceed
with another attempt to install SP2. ... (microsoft.public.windowsxp.basics)