Charlotte Foust
cfoust at infostatsystems.com
Mon Jun 2 11:01:51 CDT 2003
It used to be available upon request to MS, but they discontinued that when SR-3 was released. But if you're using OXP, what difference do the O2k security patches make to you? They won't be installed anyhow unless you're still using O2k. If you ARE still using O2k, you've got a problem. I might have a download of the patch floating around somewhere, but I may have ditched it after installing SR-3. Charlotte Foust -----Original Message----- From: John Colby [mailto:jcolby at colbyconsulting.com] Sent: Monday, June 02, 2003 7:33 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] corrupted database Is the patch for this specific problem available separately? I hate the SP2 and beyond security crap for Outlook. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Monday, June 02, 2003 11:17 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] corrupted database John, It's the latest Service Release for O2k you need installed, and that's SR-3. The patches are not in the OXP service packs because it's A2k that has to be patched, not AXP. Charlotte Foust -----Original Message----- From: John Colby [mailto:jcolby at colbyconsulting.com] Sent: Monday, June 02, 2003 6:07 AM To: AccessD Subject: [AccessD] corrupted database As we all know, there is an issue where having A2K and AXP installed on the computer at the same time, then using A2K can, in some instances, corrupt the database. It has to do with a VBA.dll being installed by AXP that is not correct for A2K's use. It was my understanding (based on messages from list members) that if you had the latest service packs applied to AXP, the problem went away. AFAIK I have the latest SP applied to officeXP (SP2.X). Today I was operating in A2K and tried to import forms from another database and got the corruption. It hosed the db. I was able to get where I needed to go by: Deleting the imported forms / reports from the corrupted db. Creating a new database using AXP Using XP, importing all the objects from the corrupted database. Using XP, importing the forms from the second db that caused the corruption when imported using A2K So... is the bug still there? I have to assume it is! John W. Colby www.colbyconsulting.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com