Re: Interesting approach for compacting on close

I wish "Why not stop wishing, and instead, design your app properly in
the first place?? were the worst thing David had ever said to me but I
think it would rank about 1653 ... in the ?best? category.

In general, I support the notion of repairing basic problems rather than
the application of corrective procedures.

On the other hand, I often set ?Compact on Close? and have done so with
applications that have run tens of thousands of times, and been closed
tens of thousands of times too, without any problem at all.

I?ve taken the disapproval of MVPs and other experienced developers for
?Compact On Close? to be just another one of the superstitions they
promulgate, superstitions that they use to enhance and maintain their
prestige and power, superstitions like ODBC is cool, ADO is dead, Forms
(?Name of Form?).Control.(?name of SubForm?).Control syntax is sound,
CurrentDB is useful, web-enabled SQL-Servers are insecure etc. Most of
these one can just ignore.

I suppose someone will now post a well-designed, error-free, compiled or
compilable, accdb or mdb (with Compact On Close set) and say, ?Open and
close this one hundred times, Lyle, and it will corrupt!? And I?ll be
convinced. This has never happened before with any other FOMVPI, of
course, but why not now?

It?s interesting that one kind of close fires the compact, while another
does not, but until I see the sample db that explodes on Compact, I?ll
just Compact (always) on Close.

BTW, I find that 2007 compacts ADPs to about two-thirds the size that
2002 and 2000 compact them. Perhaps 2003 also make the smaller compacted
version. My guess is that it does not and that the notion that ADPs got
zero upgrades in 2007 is suspect.

I have used temp tables once. I handled the bloat problem they can cause
by creating them and their indexes within a Transaction which I Rolled
Back after use. They were, of course, never saved to the db file, and
caused no bloat.

Blah ? Blah.

"Andy" <PCESoft@xxxxxxxxxxxxxxx> wrote in
news:_pxOk.1772$%11.498@xxxxxxxxxxxxxxxxxxxx:

I took exception mainly to: "Why not stop wishing, and instead, design
your app properly in the
first place? ". I hope, while you agree with his post, you don't
agree with jabs like that. Not quite the definition of constructive,
as this forum should be. I'm a regular poster as well, by the way, and
have made a living developing in Access since the mid-90's. So I had
to call him on that one. The program in question is in it's 8th year,
so I wouldn't call them band-aids, but rather 8 years of keeping my
customer's happy by implementing their feature requests.

I've always respected your posts, Lyle (I just recently changed my
post name from ARC to Andy, so we've corresponded before). Anyway,
just saying my piece.

"Andy" <PCESoft@xxxxxxxxxxxxxxx> wrote in
news:u5wOk.1761$%11.2@xxxxxxxxxxxxxxxxxxxx:

I don't think your post is very helpful, even though you feel so
strongly about the compacting feature (I guess Microsoft never
should have spent even a dollar on developing a compact for the FE).
As I mentioned, the temp tables are already off-loaded into a
workspace.accdb (separate database from the FE). Your suggestions on
"Designing an App Properly" are really great. I'm honored that a
super-programmer has replied to this humble topic; one who has
designed his apps so perfectly, that they never need updating, new
features or enhancements.

I think, David, this topic is intended for those interested in
compacting problems & solutions and maybe not necessarily for
yourself (maybe those with large FE/BE applications with 100's of
forms, queries, reports, and on the order of 100,000 lines of code).

--
lyle fairfield





--
lyle fairfield
.

Relevant Pages

  • Re: Replication Error after Adding New Table A2002
    ... Remember that design changes are serial, so that it tries to add the tables ... and then delete them (sometimes compact and repair of the DM can avoit that, ... Since the error, I've even deleted the new> tables, compact/repaired twice, and synch still fails with the "Design> changes could not be made..." ... BTW, this Design Master is a table-only> backend, and is not experiencing the Replication Conflict Viewer problem> that a different DM is producing. ...
    (microsoft.public.access.replication)
  • Re: Interesting approach for compacting on close
    ... I have a routine, "SetCurrencyandDates" that goes through a form, and sets the proper date format that the user selects in the Setup screen, and set's currency fields to the proper regional setting. ... In my testing, setting a threshold on the size of the program .accde, then only firing the compact on close if it exceeds, seems to work like a charm. ... I should comment out the SetCurrencyandDates function that runs when a form is opened and see if that has an affect on bloat. ... some other design error. ...
    (comp.databases.ms-access)
  • SHENTOP,WY-802-D Cup Sealing Machine,cup sealer
    ... A new design, beautiful shape, compact size. ... Strict quality ... our manual cup sealing machine,with compact design and luxury generous ...
    (uk.transport)
  • Re: UPS sine wave vs square wave output?
    ... 'Auto-EMC' can be quite a problem with compact ... The switcher was about a 100KHz "constant frequency" design. ... loads it had all sorts of subharmonic oscillations and chaos. ... It was a 2 foot tall 19 inch rack which had a lot of air space ...
    (sci.electronics.design)
  • Re: Uniform Lipschitz continuity
    ... David C. Ullrich wrote: ... For each D which is a compact subset of R^n there exists a constant L ... Here Bis the open ball with center x and radius r. ...
    (sci.math)