Re: Undeletable Form

You are correct that the /Decompile switch helps in many cases. There are
also other ways to force a decompile. You will find though, that with the
2002/2003 file format, that a /Decompile and Compact won't do as good a job
as it did in earlier versions. With the 2002/2003 file format you will have
better luck transferring everything to a new file.

http://support.microsoft.com/default.aspx?scid=kb;en-us;810415

--
Wayne Morgan
MS Access MVP


"Peter Hallett" <PeterHallett@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3AA9F522-68BC-4674-85B7-32FBCFE61050@xxxxxxxxxxxxxxxx
> This response is really directed to all who have contributed to this
> thread
> but you refer specifically to compaction and I may be able to contribute
> something useful in that area.
>
> When starting to use Access in earnest, I soon became aware of its
> tendency
> to 'bloat'. Adding a few forms or making one or two changes could pile on
> megabytes. An even less welcome discovery was that compaction did not
> remove
> all this bloat. Eventually I finished up with a database which was nearly
> twice the size it should have been and I could not get rid of the excess.
> Finally it led to serious malfunction. I was in deep trouble and unable
> to
> get out of it. Compaction did nothing.
>
> By persevering, I finally managed to get the assistance of a Microsoft
> guru
> (as opposed to front line support where the guy usually opens up by asking
> whether you have put the plug in the wall socket and switched on - or the
> programming equivalent thereof.) This expert made me aware of an
> undocumented MS feature which he felt might deal with my by then
> well-corrupted database but he warned that it was undocumented because one
> of
> its side effects was its ability to destroy corrupted databases as an
> alternative to repairing them.
>
> The technique is to open the database using the /Decompile switch and then
> to recompile the result. On my first attempt, my corrupted database shed
> 1.5Mb and then ran like a dream.
>
> The reconmmendation was that, once used, the utility should be deleted, to
> avoid inadvertent use. If it can be lethal in some circumstances, I must
> say
> that I have never found it anything but brilliant. I have therefore set
> up a
> shortcut to the command line decompile and named it the 'Carwash'. As I
> develop so I put each amended version through the Carwash and every time
> it
> sheds pounds. I have located the shortcut in my Unused Desktop Icons
> folder,
> where I think it is reasonably safe. By clicking Properties I can easily
> amend the command line to accept the current version of each database, as
> I
> wish to clean it up. This avoids having to reinput the whole command
> line,
> which can be lengthy and the process therefore prone to error.
>
> Since starting to use the Carwash, bloat has become a thing of the past
> and
> malfunction due to corruption is now virtually unknown. However, I pass
> this
> on 'As Is'. Don't blame me if you try it and destroy your database. The
> man
> from Microsoft indicated that it was a distinct possibility but I must
> reiterate that I have never had a moment's bother. Mind you, by using it
> regularly, I probably avoid ever presenting it with a seriously corrupted
> database.
>
> One last word on compaction. I have selected the option for automatic
> compaction every time I close my database. This is useful but the Carwash
> always shrinks the result further, sometimes substantially. Experience
> suggests that what it sheds is unwanted junk.
> --
> Peter Hallett


.

Relevant Pages

  • RE: Undeletable Form
    ... An even less welcome discovery was that compaction did not remove ... Eventually I finished up with a database which was nearly ... > It's an object already marked for deletion by Jet. ... > delete class objects from the Project Explorer window. ...
    (microsoft.public.access.forms)
  • Re: Backup Linked BE Tables
    ... be shown to be closed via code, the program execution stack and memory used ... database at the same time. ... and then you should be able to run that compaction code you have. ... I'll have to assume that you have some connection code that opens up the ...
    (microsoft.public.access.modulesdaovba)
  • Interesting issue with compaction. Any ideas to eliminate?
    ... an access frontend database which resides on a DFS target that utilizes ... For those who are unaware of DFS or FRS, ... What I am seeing is that when the compaction occurs, ...
    (comp.databases.ms-access)
  • Re: How are .ldb files unloaded
    ... I am trying to do some JRO activities and also ... still persisting either an open connection OR there is some problem ... database which keeps it extant at the time that I am trying to run my ... JRO compaction ...
    (microsoft.public.data.ado)
  • Re: same old "Data has been changed error message", way around this?
    ... form, closing the database, finding or moving to another record, setting the ... Im searching for records, viewing results in a listbox, ... -Wants to run a report of only SOME of the matching records, ... Ideally I would just switch this ...
    (microsoft.public.access.formscoding)