Charlotte Foust
cfoust at infostatsystems.com
Thu Jun 2 13:25:45 CDT 2005
I seem to recall that it reinstitutes a bug or two cured in earlier SPs, perhaps something to do with resetting the autonumber seed, but I don't recall. Charlotte Foust -----Original Message----- From: Francisco Tapia [mailto:fhtapia at gmail.com] Sent: Thursday, June 02, 2005 10:20 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Error Loading Project? I was skeptical because I've been on SR1a for sooo long now, but I did upgrade to SP3 and everything is now working as expected :). Just hope this does not contribute to some additional bug :S On 6/2/05, Francisco Tapia <fhtapia at gmail.com> wrote: > SP3 :O > I've only patched up to SR-1 on 2000 before... anything I should watch > out for in SP3? > > On 6/2/05, Charlotte Foust <cfoust at infostatsystems.com> wrote: > > If you have 2k and XP on your either machine, make sure 2k is > > patched to SP3 before you do any exporting. OXP installed a > > VBE6.dll that breaks the version in 2k, causing that blasted network > > connection error to be thrown erroneously. Take a look at this MSKB > > article: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;304548 > > > > Charlotte Foust > > > > > > -----Original Message----- > > From: Francisco Tapia [mailto:fhtapia at gmail.com] > > Sent: Wednesday, June 01, 2005 5: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 > > > > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > -- -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