[AccessD] AccessD Digest, Vol 84, Issue 23

Would you like to try RemoteEatBloat and stick it into its own newly created
form and then see if that reduces it (auto compacts and repairs) so you can
see what size it is.

If it is reduced, then you could manually import it back into your main  mdb

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert
Sent: 16 February 2010 17:44
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] AccessD Digest, Vol 84, Issue 23

>
> Max (MGA):
> I have a similar problem but it is because  of a corrupt  form.  Therefore
> RemoteEATbloat bombs out.  If I remove the offending form, it will compact
> ok.
> So, my question is, with your problem mdb is the problem the form or
> EatBloat? Trying to pin down what else I can do to improve it.
>

Now I see what you're driving at.

The form is not corrupt in the sense that it doesn't work, or can't be
loaded. It functions fine. It is huge.

And, EatBloat (SaveAsText/LoadFromText) works fine on the problem form -- no
errors, and the form is OK. It just doesn't fix the bloat problem. Edit the
problem form 2 or 3 times after EatBloat, and the database quadruples in
size. This is even for trivial changes, like moving a control, or modifying
a single line in code.

The only conclusion I can reach is that, on A2K, there are certain bloat
problems that SaveAsText/LoadFromText can't fix.

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