[AccessD] Strange corruption

Joe,

I have had some similar problems recently.  No proper solutions but I 
found that if I opened the database (shift-key down) and then opened one 
of the modules, commented the entire module out, compacted and closed...I 
was then able to open the database again, uncomment the module and it 
worked fine?!

I know this sounds like voodoo, but it has happened more than once and 
doing this seems to work...not sure why, can only assume it has something 
to do with the code being compiled, but the fact that it compiles and runs 
fine after all that that is a little wierd to say the least.

HTH
Ryan






"Joseph O'Connell" <joconnell at indy.rr.com>
Sent by: accessd-bounces at databaseadvisors.com
24/02/2004 17:15
Please respond to Access Developers discussion and problem solving 

 
        To:     "Microsoft Access Database Discussion List" 
<ACCESS-L at PEACH.EASE.LSOFT.COM>, <accessd at databaseadvisors.com>
        cc: 
        Subject:        [AccessD] Strange corruption


Cross posted AccessD and Access-L


I recently sent a zipped Access 2000 database to a friend.  He was able to
unzip and run the Access application with no problem, but he had a 
question
about the code.  So that I could look at the code while talking with him, 
I
opened the oroiginal version on the computer that was used for 
development,
a Win XP Pro laptop.  When I attempted to open any module, the message box
informing me that there is a fatal error in Access appeared, the only
options are whether or not to send a report to Microsoft.  After trying 
this
several times with the same result, I thought that the database might have
become corrupted so I extracted the Access application from the zip file 
and
tried again.  Same result.

Copying the zip file to a Windows 2000 Terminal Server, unzipping and 
trying
to look at a module generated the same error.  I then unzipped again, but
before attempting to open a module, I verified that several local tables
were intact and could be opened with no problem.  Opening forms which are
bound to queries that use the tables also did not produce any error. After
opening tables and forms, the modules then opened as expected without any
errors!

I tried the same procedure on the Win XP machine--unzip, look at a table,
open a form, open a module.  No error, it worked as expected.

Has anyone else experienced strange behavior like this?  Any ideas as to
what could cause this situation?

Joe O'Connell



-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



 

  
This e-mail and any attachment are confidential and contain proprietary information, some or all of which may be legally privileged.  It is intended solely for the use of the individual or entity to which it is addressed.  If you are not the intended recipient, please notify the author immediately by telephone or by replying to this e-mail, and then delete all copies of the e-mail on your system.  If you are not the intended recipient, you must not use, disclose, distribute, copy, print or rely on this e-mail.

Whilst we have taken reasonable precautions to ensure that this e-mail and any attachment has been checked for viruses, we cannot guarantee that they are virus free and we cannot accept liability for any damage sustained as a result of software viruses.  We would advise that you carry out your own virus checks, especially before opening an attachment.

The UK firm Ernst & Young LLP is a limited liability partnership registered in England and Wales with registered number OC300001 and is a member practice of Ernst & Young Global.  A list of members? names is available for inspection at 1 More London Place, London, SE1 2AF, the firm?s principal place of business and its registered office.