[AccessD] EatBloat latest version?? availability --- EIasT - further review

Dan Waters df.waters at comcast.net
Sat Nov 19 09:44:49 CST 2011


Hi Jack,

Glad you liked this so far!

I had thought about putting the object names in the status bar.  It seems as
though if the name of the object that failed had been there, that would have
given you a clue as to which object had gone bad.

The line numbers come from an Access utility called M-Z Tools for VBA.  I
use it constantly.  And it's free - with a requested donation.
http://www.mztools.com/index.aspx

Also - I reread my instructions and forgot to say that this exports all
objects except tables.  It's been my experience that table bloat and
problems are best solved with Compact & Repair.

Would it be possible for you to send a copy of the Demo.mdb for me to test
on?  I don't think I could fix it, but it helps when testing to have a 'real
world' example.

If you change .mdb to .pdf it will get through just fine.

Thanks for your feedback,
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jack and Pat
Sent: Saturday, November 19, 2011 8:12 AM
To: AccessD Group Discussion
Subject: Re: [AccessD] EatBloat latest version?? availability --- EIasT -
further review

Dan,

 

Further to my (off list) note from late last night, I did a little more
review. I opened the EIasT.mdb with a breakpoint to allow stepping thru the
code. In the problem data base, the queries and forms - up to the problem
form - are all exported as text as expected. After the error, the code stops
on a STOP statement, as it should. If I step through, it continues with the
next procedure in code and does Import the text that was previously
exported.

 

It seems I have a corrupted Form and that its source can not be retrieved. I
did not find any resolution to the "there isn't enough memory to perform
this operation. Close unneeded programs and try the operation again". Seems
the consensus is to rebuild the form involved.

 

So from an EIasT view, I did use the utility against another database and
all was well. It did build a directory and saved all queries, forms, reports
and nodules (I don't have any macros), It did import all the text. It does
Compact and Repair. And the database , original and rebuilt are available.
Good stuuf.

 

I'm impressed with your code. No wasted code; very concise. I especially
like the line numbers in the vba. I take it that is based on your use of FMC
utilities. The progress bars are a nice feature - seems there are lots of
people trying to build these based on forums I've seen.

 

Again, thanks for responding quickly, and thanks for the EIasT code.
Perhaps it should be made available at databaseadvisors as a utility. 

 

Jack 

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




More information about the AccessD mailing list