[AccessD] AccessD Digest, Vol 84, Issue 23

Hi Ken,
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.

Thanks

Max


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

>
> Max Wanadoo:
> >Ken:
> >SaveAsText/LoadFromText does NOT:
> > a) Fix all kinds of bloat
> > b) Reset the form lifetime control count limit
>
> a) What kinds of bloat does it NOT fix?  Can you provide any examples -
> thanks.
>

I have first-hand experience with one unfixable front end. Unfortunately, it
is a proprietary application, and I am not working for the company anymore,
so I can't provide a test file.

The problems centered around big forms (500 or 600 controls) with long, long
development histories, in a front end with 200+ forms, and 500+ reports.
Beyond that, I couldn't identify a specific cause.

However, in following this list, I recall at least two other people who
tried EatBloat, and reported that it failed. So I am reasonably confident I
am not alone in experiencing this.

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