[AccessD] Mde trouble

We have many experiences over this, spacially if we use Office XP Spanish
version. We solve normally using one computer with Office XP English
version. 
1- Creating a new MDB file and importing all from the last MDB corrupted, 
2- then check all forms that have OCX/COM controls and then replace with a
new control, 
3- check the names of this for code problems of every control in forms
(common controls, progress bar, etc...)
4- Check other missing references
5- Debug and Compile

We all obtain a new MDB perfect to use. We are decompiling every week our
main MDB and makes copies every version, because the stability of MDB when
you program and use many external controls is very low.

Good luck and hope that this solve your problem

Juan Menendez
Mastercafe SL

===========================================
MASTERCAFE SL - NIF B-82.617.614
www.mastercafe.com
Deleg. Asturias 
Tel 985.88.49.44 / 627.531.764
Fax 627.500.205
info at mastercafe.com
juan at mastercafe.com
Deleg. Madrid
Tel 627.474.285
cecilia at mastercafe.com
===========================================


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
rsmethurst at UK.EY.COM
Sent: martes, 10 de febrero de 2004 17:51
To: Access Developers discussion and problem solving
Subject: [AccessD] Mde trouble


I'm using A2K and am working with a database that fluctuates between about
    10 and 18 megs.  It has been working fine, until I tried to create an 
.mde
    with it.
 
 The first .mde attempt, seemed to work ok, but literally didn't compact 
the
    database more than a few thousand bytes (apparrently it normally makes
    substantially more difference than that)
 
And now, I am simply getting a message saying that 'MS Access was unable 
to
    make an MDE file', even though there appears to be no problem with it, 
and the code compiles fine?!
 
I have tried importing the objects, and a new database creates an mde with
    just the tables. But fails with the forms, and fails with the modules 
when I have tried on
    seperate databases.

Other than this problem, the database seems to work fine and isn't having
    any problems compacting either.

Can anyone offer any suggestions?
Many thanks (in advance)
 

  
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.
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com