Charlotte Foust
cfoust at infostatsystems.com
Thu Jun 2 17:14:07 CDT 2005
Well, it has been discussed here in the past, but the gist is that both XP and 2003 provide a VBE6.dll that is a different version from that used by Office 2000. This is not strictly an Access problem, since I've seen reports of it toasting Excel and Word as well. The errors arise with both Access 2000 pre-SP3 and version 6.3.91.8 of the dll. So if you have 2000 and are running it on the same machine with a later version or are passing code containers between machines with differing versions, you will run into problems on the 2000 machine unless you have SP3 installed. SP3, and also a hot patch that was available prior to SP3 release, actually patch the A2k executable so that it can cope with the later version of the dll without going down in flames. When I first ran into it, way back, I discovered that if I opened an mdb created elsewhere in Access XP on my machine, which only had 2000, and tried to view the code I was likely to regret it. If I tried to *import* the code containers into an Access 2000 database, I was SURE to regret it. The recovery steps listed in MSKB 304548 may or may not work. They didn't work for me when I encountered the problem. Charlotte Foust -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Thursday, June 02, 2005 1:00 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Error Loading Project? Charlotte, Why don't you give a synopsis of what the problem is and how it is triggered. XP provides new dll, 2K PreSP3 has wrong entry points, etc. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, June 02, 2005 3:53 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Error Loading Project? They don't break in XP and 2003, only the other direction. Charlotte Foust -----Original Message----- From: Jim Lawrence [mailto:accessd at shaw.ca] Sent: Thursday, June 02, 2005 11:32 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Error Loading Project? So what would be the best way to import Access into XP and 2003 without major issues other than hand coding? Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, June 02, 2005 11:25 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Error Loading Project? 2003 breaks it the same way as XP. Charlotte Foust -----Original Message----- From: Francisco Tapia [mailto:fhtapia at gmail.com] Sent: Thursday, June 02, 2005 8:56 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Error Loading Project? Not at this time, I Just ordered Access 2003, currenlty I have Office 97 & 2000 w/ Outlook 2003. On 6/1/05, John W. Colby <jwcolby at colbyconsulting.com> wrote: > Do you happen to have 2K and XP on the same machine? > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco > Tapia > Sent: Wednesday, June 01, 2005 8:47 PM > To: access-l at peach.ease.lsoft.com; Access Developers discussion and problem > solving > Subject: [AccessD] Error Loading Project? > > > Recently I've been plauged by this error: > > I have 2 Access ADP's , the primary is the dev copy and I write in > this copy all my development code, once compiled, and tested I > "EXPORT" the new form or modified form to the Production .adp copy > this file used to be on the network, but due to the more recent > network errors that I was plauged w/ I decided to simply create a > folder on my pc called "build" and export to that folder instead, > everything had been working great, and in fact each copy compiles w/o > errors... but if I export from the dev on drive C to the build on > drive C I end up w/ an error on the build copy as "Error Loading > Project, disk or network error, continue loading?" if you click ok I > find that the module is empty. If I then (while in the build copy), > IMPORT the same form, then I get a new Form1 classic import, I delete > the corrupted form and rename Form1 to Form and all is well again... > why can I not export anymore? > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More... -- 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 -- 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