 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 2 / March 2007Access97 Runtime Application
After installing Office2007 Professional, on an XP-Pro computer, my access97 runtime application gets an error, when I close the application. After sending the error report to Microsoft, a web page pops up that says "Problem caused by Microsoft Office 97: consider upgrading" The application ran and closed fine before I installed Office2007. I uninstalled and reinstalled my application with the same result duh do what the message says; kid On Mar 22, 2:06 pm, Access97_Forever <Access97_Fore...@discussions.microsoft.com> wrote: > After installing Office2007 Professional, on an XP-Pro computer, my access97 > runtime application gets an error, when I close the application. After > sending the error report to Microsoft, a web page pops up that says "Problem > caused by Microsoft Office 97: consider upgrading" > The application ran and closed fine before I installed Office2007. > I uninstalled and reinstalled my application with the same result Note that this person is really A a r o n K e m p f and that he is not an employee of Microsoft. Tony  SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm 97 doesn't allow Access Data Proejcts you are officially 100% obsolete if you use Acc97 for anything On Mar 22, 2:06 pm, Access97_Forever <Access97_Fore...@discussions.microsoft.com> wrote: > After installing Office2007 Professional, on an XP-Pro computer, my access97 > runtime application gets an error, when I close the application. After > sending the error report to Microsoft, a web page pops up that says "Problem > caused by Microsoft Office 97: consider upgrading" > The application ran and closed fine before I installed Office2007. > I uninstalled and reinstalled my application with the same result This is Microsoft policy: they make new releases of Access incompatible with previous versions so that programmer/user must always upgrade. Vlado > After installing Office2007 Professional, on an XP-Pro computer, my > access97 [quoted text clipped - 4 lines] > The application ran and closed fine before I installed Office2007. > I uninstalled and reinstalled my application with the same result >This is Microsoft policy: they make new releases of Access incompatible with >previous versions so that programmer/user must always upgrade. From my viewpoint MS has done a remarkably good job in making Access compatible with older versions. For example A2007 can run an A2000 MDE. A2007 can update A2000 MDBs. That's pretty darned flexible. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm I'm affraid you may have forgotten A97 -> A2000 (and higher) incompatibility and all the problems with A97 applications on systems where newer versions of Access have been installed after the A97 app installation. You must re-install A97 app on such systems. And, worst of all, all versions of Access share some parts of registry so that there's a need of a partial re-install of higher version of Access after you ran A97 app. IMHO, Access is not fully compatible and sometimes it consumes a lot of time to make it work!!! If I only knew it 10 years ago... I would never buy Access!!! Vlado >>This is Microsoft policy: they make new releases of Access incompatible >>with [quoted text clipped - 7 lines] > > Tony >I'm affraid you may have forgotten A97 -> A2000 (and higher) incompatibility >and all the problems with A97 applications on systems where newer versions >of Access have been installed after the A97 app installation. You must >re-install A97 app on such systems. There's a KB article and an article at the Access web explaining how to fix that problem so to me that's not a big deal. >And, worst of all, all versions of >Access share some parts of registry so that there's a need of a partial >re-install of higher version of Access after you ran A97 app. There is a problem between A2002 and A2003 and another one between A2007 and A2003 but I wasn't aware of the A97 problem. I used to run those lots one right after the other. >IMHO, Access is not fully compatible and sometimes it consumes a lot of time >to make it work!!! If I only knew it 10 years ago... I would never buy >Access!!! To each thier own opinion. The problems you mention are easily surmountable. Although the delay when running A2007 after A2003 is highly irritating. There is no better database development tool out there. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm > "There's a KB article and an article at the Access web explaining how to > fix that > problem so to me that's not a big deal." Could you point me to the KB article, pls? TIA Vlado >>I'm affraid you may have forgotten A97 -> A2000 (and higher) >>incompatibility [quoted text clipped - 28 lines] > > Tony >> "There's a KB article and an article at the Access web explaining how to >> fix that >> problem so to me that's not a big deal." >Could you point me to the KB article, pls? Bugs: License problems http://www.mvps.org/access/bugs/bugs0013.htm ACC97: AcLicn97.exe Available in Download Center http://support.microsoft.com/?kbid=191224 ACC: "There Is No License" Error Message Starting Microsoft Access http://support.microsoft.com/?kbid=141373 Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm > Although the delay when running A2007 after A2003 is highly irritating. Does Microsoft know about this "issue"? BTW. I my speach all "issues" are bugs... even in my apps. ;-) How long it takes to run A2007 after A2003? Could you give us some details, pls? Vlado >>I'm affraid you may have forgotten A97 -> A2000 (and higher) >>incompatibility [quoted text clipped - 28 lines] > > Tony >> Although the delay when running A2007 after A2003 is highly irritating. >Does Microsoft know about this "issue"? Ohhh yes. We told them. Loudly. <smile> >How long it takes to run A2007 after A2003? Could you give us some details, >pls? On my dual core laptap less than a year old it takes about 56 seconds to switch. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm I just think that you guys are just ridiculous DONT PUT MULTIPLE VERSIONS ON THE SAME MACHINE what do you need an extra desktop to run Access 97 on? ROFL > >> Although the delay when running A2007 after A2003 is highly irritating. > >Does Microsoft know about this "issue"? [quoted text clipped - 12 lines] > read the entire thread of messages. > Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm A a r o n K e m p f wrote: >I just think that you guys are just ridiculous > >DONT PUT MULTIPLE VERSIONS ON THE SAME MACHINE > >what do you need an extra desktop to run Access 97 on? <shrug> I currently have five different Access versions on my system. I've been doing this for quite a number of years. This problem between A2007 and A2003 is, so far, the worst problem. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm >BTW. I my speach all "issues" are bugs... even in my apps. ;-) My apps only have issues, never bugs. MS has lots of bugs though. <smile> Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm there IS a better database development tool it is called SQL Server Management Studio Express; it is free with SQL Server Express Access Data Projects have 10 times the functionality and ease of use as Access MDB > >I'm affraid you may have forgotten A97 -> A2000 (and higher) incompatibility > >and all the problems with A97 applications on systems where newer versions [quoted text clipped - 26 lines] > read the entire thread of messages. > Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm > I'm affraid you may have forgotten A97 -> A2000 (and higher) > incompatibility and all the problems with A97 applications on systems [quoted text clipped - 8 lines] > > Vlado If you are a serious developer that needs to support multiple versions of Access and/or multiple versions of Windows then the only practical path to follow is to create an Install CD that includes the Access 97 runtime and versions of your MDE file in both Access 97 and Access 2000. This gives you full coverage with only two versions of the file and only one version of the runtime. For users that already have an installation of Access 97 you install just the 97 MDE and any support files (no compatibility issues at all). For users that already have an installation of Access 2000, 2002, 2003, or 2007 you install just the 2000 MDE and any support files (no compatibility issues at all). For users that do not have any version of Access you install the Access 97 runtime and the 97 MDE (no compatibility issues at all). If your app requires (or your users desire) some of the features only available in the newer versions then you will start to lose coverage at the lower end of the version spectrum, but that will be due to decisions made by you and/or your users, not because Microsoft didn't do a good job on compatibility issues. If a future version of Windows no longer supports the older versions that again will require you to start dropping support for those versions on that platform, but so far that situation has not been a big issue. The only time real compatibility issues arise is when you try to install an Access runtime on a PC that already has a version of Access on it and that should hardly ever be necessary. If you (the developer) want to develop in ONLY ONE version and have that also be the newest version then you are cutting your own throat. That is only a valid option in a corporate environment where the configuration of all PCs is kept consistent and everyone upgrades at the same time. SignatureRick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com I fixed the problem by adding a hidden form, opened during the application startup routines, with an event as follows Private Sub Form_Unload(Cancel As Integer) Application.Quit acQuitSaveAll End Sub ======= > > I'm affraid you may have forgotten A97 -> A2000 (and higher) > > incompatibility and all the problems with A97 applications on systems [quoted text clipped - 43 lines] > environment where the configuration of all PCs is kept consistent and > everyone upgrades at the same time. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.