Are Access Bugs Fixed (XP)

Topic

New Reply

Although I can’t answer the questions in your post, there is a very interesting free article at Smart Access written by Mike Gunderloy that looks at a number of changes. His bottom line take is, although there aren’t a lot of reasons to upgrade from 2000, fortunately there’s no reason not to for a change.

Reply | Quote

Replies

A very good article. I have a specially licensed copy of A2K from my previous employer – but I succeeded in wrecking it, and no longer have the installation disks to do a detect and repair . My new employer has given me a laptop, which has A2K installed from the network, and therefore I do not have the CDs for that either .

I was considering various options, but now know that A2002 is the way to go. I occasionally do literature analyses that involve large numbers of pivot tables. The only way I found to get them to work as I wanted with A2K was to use Excel: unfortunately, moving either the spreadsheet or database to different directories resulted in having to rebuild the pivot tables .

Only issue now is whether the Corel suite that came with the computer is an OEM version or is recognized as a legitimate upgrade. Of course, if I don’t delete the broken A2K, maybe it will recognize it as being ‘legal’??

kiwi44

Reply | Quote

Well, I have answered the question about whether M$ allows competitive upgrades – no, they do not! The only ‘acceptable’ upgrade to XP is from Office 2000/97

Reply | Quote

You are correct….AND there may be a way around the competitive upgrade if you act quickly, according to the folks at http://www.cheaperoffice.com/html/XPUpgradeGuide.asp
It involves purchasing an Office2000 competitive upgrade before 6/30/2001, and then requesting a FREE upgrade to the equivalent version of OfficeXP before 6/30/2001. This may or may not be the current rules, but is definitely worth checking out!

Regards,

Reply | Quote

Does anyone know what bugs from Access 2000 have been fixed in Access 2002? Specifically, have the problems with incorrectly changing the Modified and Created Dates in the database container window been fixed and the problems with failing to prompt for saving queries been eliminated.

Reply | Quote