Re: Maintenance Recomendations -Compact?
- From: "Larry Daugherty" <Larry.NoSpam.Daugherty@xxxxxxxxxxx>
- Date: Mon, 25 Feb 2008 12:07:56 -0800
If by "maint. recs" you actually mean Maintenance Requirements, please
type it that way. We don't "text" and we're not big on abbreviations
nor jargon that lies far afield from Access. That allows us to
quickly understand your question and, just possibly, to address it.
:-)
Most likely, your database is still monolithic; meaning that you
haven't split it into FrontEnd and BackEnd. If that is true then
setting "Compact on Close" is a very good idea. The only overhead is
the time it takes; not much at all. That frequent Compact and Repair
will go a long ways toward preventing your database becoming corrupt
in the first place. Compact and Repair doesn't cause problems, it
solves those it can solve and reports those it can't. That early
warning might be sufficient that you can save all of your data and
design.
The important things are your design and your data. The size of
either is never the issue except when you lose it. The computer works
exactly as hard in the idle state as it does when doing meaningful
work. So, in addition to the above, take frequent backups of your
application. In this case you need to name and save the backups
separately so that you can step backward through backups in the event
of loss of data.
You can't backup the current database while it is running so the
button on a form question doesn't apply.
I was surprised to see that you intend to deliver a commercial
application. Yes, we senior citizens appreciate clear, understandable
buttons and other elements of the user interface. In my years of
developing applications, I've found that users of all ages do better
when things are clear and unambiguous at all levels.
Given that you intend to flog your application to other users then I
recommend that you go through the process of splitting the database.
There are instructions in Access. If you don't split it then
maintenance becomes a nightmare. There are only two reasons for not
splitting an Access database: 1) It is so badly done that there will
never be users who request additional features and there is no intent
to fix outright bugs. 2) It is so perfectly done that it has
anticipated all future needs and there are no bugs at all. I've seen
lots of #1s and absolutely no #2s.
Now, the sad news is that once you do split your database into a
FrontEnd (the Forms, Queries, Reports) and BackEnd (just the tables),
the Compact on Close feature is now useless to the Data in the tables
which is really the most important part of the User's installation.
To provide the required coverage you need to either program a solution
or to get one of the available solutions.
Good luck with your application.
HTH
--
-Larry-
--
"Touche'' Techie" <ToucheTechie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:0D3E6355-73C1-4AA7-A213-803776C019EE@xxxxxxxxxxxxxxxx
What are the maint. recs for an Access DB?perhaps a bit
It seems that setting the compact on close is a good idea, but
of overkill on a small DB (now only 10mb but 25-40mb est. in 2years). Is
there added risk with the frequent compacting? Is the compact onclose also a
repair or just compact?DB, but
It also seems the rec is to back-up and then compact from what I've
read....True?
I was hoping to program a form button to be a backup button for the
reading the posts I'm not sure that is a good idea or how to do it.Advice?
intend
An ERP DB will be handed off to some senior citizens and they do not
to have regular techie check-ups so anything I can do to keep itrunning on
its own would be good. Obviously simple solutions like big buttonswork best
too.
Thanks
.
- Follow-Ups:
- Re: Maintenance Recomendations -Compact?
- From: Touche'' Techie
- Re: Maintenance Recomendations -Compact?
- Prev by Date: Learning about databases & building a simple one
- Next by Date: Re: CONDITIONAL FORMATTING
- Previous by thread: Re: Maintenance Recomendations -Compact?
- Next by thread: Re: Maintenance Recomendations -Compact?
- Index(es):
Relevant Pages
|
