Re: maximum number of controls on a form
- From: "Mark Kubicki" <Mark@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 22 Jun 2009 16:55:19 -0400
Thanks for your insight to the stability of Access (I actually, in my naive
exposure) agree, it is.
The crashes that I have are solely related to forms, and always occur during
the save process (either after lengthy editing, or simply after adding a
single control.) Usually access shuts down and asks to back-up and
recover... Sometimes the form is usable when the project reopens, sometimes
it is not. Occasionally, the form takes a long time (several minutes to
save, often it saves in a matter of seconds; usually, the two scenarios
happen in cycles: it continually takes a long time, then suddenly, it starts
saving quickly, only to revert, after "some" increment, back to lengthy save
times.(this makes me think I do have an "issue".
Of course, I have no idea where to look, and if you have any additional
thoughts on this, they would also be greatly appreciated...
Mark.
----------------------------------------------------------------------------------------------
"Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx> wrote in message
news:eJp6%23LM8JHA.1340@xxxxxxxxxxxxxxxxxxxxxxx
that "life" is re-set if you open the from in design mode, and do a
save-as.
Now, delete the original form, and then simply re-name the one you just
saved.
You should do compact and repair at this point.
Q.
- is there a way to tell what Access thinks is the current count of
controls?
Yes, the above will do so.
- can the number be reset to what is currently on the form ONLY?
Yes, just do a save-as as per above.
- could there be something else that is causing the crashes (having to
restore back-ups is almost a daily occurrence (now days, I back-up allot
!!!)
I find access VERY stable. Two things:
If access does crash, then you REALLY need to do a de-compile on that
application (as it now damaged). Make sure you hold down the shift key
when you do the de-compile to ensure no startup code runs at all. I then
suggest you exit..and again re-enter (again shift key). Now do a compact
repair.
So, if access crashes, then your application now going to be un-stable
until you do the above.
Also, if this is multi-user, then split the application, and distribute
mde to EACH desktop. I had customers running applications with my all day
long with about 4-5 users for 9 years straight, and I don't the
application has ever hung up once. Mind you small applications with 50-60
highly related tables and tiny table sizes of 65,000 records is small, but
in this case the applicaon does have about 160 forms, and I not have one
phone call in 9 years that it every hung up.
So, in my experience I find access very stable indeed. If you having
problems of stability, something is wrong here...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- References:
- maximum number of controls on a form
- From: Mark Kubicki
- Re: maximum number of controls on a form
- From: Albert D. Kallal
- maximum number of controls on a form
- Prev by Date: Re: Subform with no records
- Next by Date: Re: Create an invoice
- Previous by thread: Re: maximum number of controls on a form
- Next by thread: help with type mismatch in .findfirst lookup
- Index(es):
Relevant Pages
|
Loading
