[AccessD] RemoteEatBloat

Ken,

When I  wrote EatBloat and again for RemoteEatBloat I specifically stated it
was for A2k3 and it tests for this and  puts your current version on the
title bar Eatbloat)

I  don't know if Dan has made it less specific on the rewrite, but it may
well be that he didn't and you may be having compatibility problems.

Would you like me to send you on RemoteEatBloat to test? It is not yet
finished and I have to handle Relationships and linking.

So far it (RemoteEatBloat) handles For Export:-

Tables (Local only - specifically does NOT do linked tables otherwise
Imports to new mdb would be incorrect).
Queries
Forms
Reports
Macros
Modules
References
Relationships (wip)
Links (wip)
It does not handle Pages (DAP) and I have no intention of bothering with
that.

It is a standalone unlike the Eatboat which required to sit inside the
source mdb.
It prompts for a source mdb
Exports selected objects as listed above (tables can be csv, xls, xml or all
of them)

For imports:
It prompts for a new mdb.
Imports exported objects into the new mdb.
Compacts and Repairs
Deletes the working  file.
Again, the Relationships (wip) and Links (wip) are work in progress.

The  source mdb  is not changed in any way.
It is an  Access  program and therefore if the source file has an access
problem then it is most unlikely that this program will overcome that.

Let me know if you want a copy

Max



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert
Sent: 18 February 2010 18:08
To: accessd at databaseadvisors.com
Subject: [AccessD] RemoteEatBloat

Max,

Where do i get RemoteEatBloat? Does it work for Access 2000? If so, I'm
willing to look at it.

But to reiterate, SaveAsText/LoadFromText worked properly for the problem
form. The database was reduced in size similar to decompile/compact &
repair.

However, the bloating did not go away. Subsequent edits to the form caused
rapid file size increases and a drastic slow down in save times.

-Ken


From: "Max Wanadoo" <max.wanadoo at gmail.com>
> Subject: Re: [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
>
>
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com