Hi Everyone,



I need to convert a database that I created from 97 into 2000, something

I've done many times with no problems in the past. But this particular

database won't convert properly. At the end of the conversion I get a

message about compiling errors. Then when I go into the code, it is

completely messed up: some lines have been partially cut off, extra subs

appear which create ambiguous sub names, junk characters appear at the

bottom of the module, etc. It's a mess. What might have caused this? In 97

the database works perfectly with no compile errors.



Thanks in advance!



Miriam Engelberg



-----Original Message-----

From: Sean Bornstein [mailto:bostonroxx@a...]

Sent: Tuesday, July 17, 2001 9:49 AM

To: Access

Subject: [access] ADP WRITE CONFLICT ADVICE





Hello all I have a form that has about 3 subforms on it and alot of 

backend VBA code that processes update procedures etc.  I keep running 

into Write Conflicts with the form and then the application bombs.  

Anybody ever run into this and find the best resolution?  I have made sure 

that all my bit fields are not null and time stamps are on all tables so 

that is not the issue.  I am trying to make sure I requery after every 

update.  Please any advice would be helpful.  Also I think because I am 

using resume statements I get locked into a loop.  Any idea how to work 

around that with some good error trapping?  Thanks all.

Hi Miriam,



It might be a corrupt database.  You can try fixing it, or just copy the

code to the access 2000 database..





-----Original Message-----

From: Miriam Engelberg [mailto:MiriamE@c...]

Sent: Tuesday, July 17, 2001 9:32 AM

To: Access

Subject: [access] Code corrupted when convert from 97 to 2000





Hi Everyone,



I need to convert a database that I created from 97 into 2000, something

I've done many times with no problems in the past. But this particular

database won't convert properly. At the end of the conversion I get a

message about compiling errors. Then when I go into the code, it is

completely messed up: some lines have been partially cut off, extra subs

appear which create ambiguous sub names, junk characters appear at the

bottom of the module, etc. It's a mess. What might have caused this? In 97

the database works perfectly with no compile errors.



Thanks in advance!



Miriam Engelberg

It's hard to know what causes corruption...  But one thing to try is to

create a blank database in A97 and import all your objects from the original

db into the new blank db.  Then see if the import bombs on a given module

(in which case that's likely the bit that's corrupted).  If all goes well

with the import, try converting the new copy of the db.



HTH,



-Roy



-----Original Message-----

From: Miriam Engelberg [mailto:MiriamE@c...]

Sent: Tuesday, July 17, 2001 9:32 AM

To: Access

Subject: [access] Code corrupted when convert from 97 to 2000





Hi Everyone,



I need to convert a database that I created from 97 into 2000, something

I've done many times with no problems in the past. But this particular

database won't convert properly. At the end of the conversion I get a

message about compiling errors. Then when I go into the code, it is

completely messed up: some lines have been partially cut off, extra subs

appear which create ambiguous sub names, junk characters appear at the

bottom of the module, etc. It's a mess. What might have caused this? In 97

the database works perfectly with no compile errors.



Thanks in advance!



Miriam Engelberg

Thanks for your help, Kent! I took your suggestion and copied the code for

the 2 corrupted modules into the 2000 version, and it fixed the problem.

However, if anyone has insight into why the problem occurred in the first

place, please let me know. (I've checked thoroughly and the 97 version has

no compile errors; the corrupted code occurs only in the 2000 version.)



Miriam Engelberg





-----Original Message-----

From: Kent Rhodes [mailto:kentrhodes@h...]

Sent: Tuesday, July 17, 2001 10:21 AM

To: Access

Subject: [access] RE: Code corrupted when convert from 97 to 2000





Hi Miriam,



It might be a corrupt database.  You can try fixing it, or just copy the

code to the access 2000 database..





-----Original Message-----

From: Miriam Engelberg [mailto:MiriamE@c...]

Sent: Tuesday, July 17, 2001 9:32 AM

To: Access

Subject: [access] Code corrupted when convert from 97 to 2000





Hi Everyone,



I need to convert a database that I created from 97 into 2000, something

I've done many times with no problems in the past. But this particular

database won't convert properly. At the end of the conversion I get a

message about compiling errors. Then when I go into the code, it is

completely messed up: some lines have been partially cut off, extra subs

appear which create ambiguous sub names, junk characters appear at the

bottom of the module, etc. It's a mess. What might have caused this? In 97

the database works perfectly with no compile errors.



Thanks in advance!



Miriam Engelberg