468,135 Members | 1,465 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,135 developers. It's quick & easy.

Access automatically shuts down after filtering or sorting a form

Hi,

I have a form that take some time to load due to many comboboxes and at
least 8 subforms.
When I filter or sort the main form I get an error message and then Access
shuts down. They ask if I want to send the error report to Microsoft. Has
anybody seen this type of error message and what can I do to prevent it from
happening. Am I doing something illegal in my code? It used to work but I
have added conditional formatting to a subform but that shouldn't cause any
problem. It ONLY happens when I try to filter or sort the main recordset
using Access built-in functions. I am using Access 2002.
Any help appreciated
Richard
Nov 12 '05 #1
5 2750
Conditional formatting in a sub-form and filtering the main form caused this
problem for me, remove the formating and then see if the problem doesn't go
away. Incidentally, I'll bet that as long as you don't apply a filter to the
main form the database will work fine even with conditional formatting in
the sub-form. I have had almost exactly the same problem, only in my case
Access 2002 would not shut down until I attempted to scroll after filtering.
You are lucky, because your post contains the cause of this problem and
because mine didn't start until I switched to 2002 it took me longer to
track down.

--
Jeffrey R. Bailey
"Richard" <rw**********@chello.se> wrote in message
news:G3sub.3792$%W3.19990@amstwist00...
Hi,

I have a form that take some time to load due to many comboboxes and at
least 8 subforms.
When I filter or sort the main form I get an error message and then Access
shuts down. They ask if I want to send the error report to Microsoft. Has
anybody seen this type of error message and what can I do to prevent it from happening. Am I doing something illegal in my code? It used to work but I
have added conditional formatting to a subform but that shouldn't cause any problem. It ONLY happens when I try to filter or sort the main recordset
using Access built-in functions. I am using Access 2002.
Any help appreciated
Richard

Nov 12 '05 #2
Incidentally what you are doing isn't illegal and the solution I described
above is only a work around. When I had the problem I searched the news
groups and knowledge bases and never found mention of anyone else having it.
I have always assumed it to be an issue related to running multiple
development environments on my main machine. I worked around conditional
formatting by adding some check boxes to reflect the state of the records in
a different way. I couldn't do without filtering the main form in my
application.

--
Jeffrey R. Bailey
"Jeffrey R. Bailey" <mr**********@yahoo.com> wrote in message
news:AP***************@twister.tampabay.rr.com...
Conditional formatting in a sub-form and filtering the main form caused this problem for me, remove the formating and then see if the problem doesn't go away. Incidentally, I'll bet that as long as you don't apply a filter to the main form the database will work fine even with conditional formatting in
the sub-form. I have had almost exactly the same problem, only in my case
Access 2002 would not shut down until I attempted to scroll after filtering. You are lucky, because your post contains the cause of this problem and
because mine didn't start until I switched to 2002 it took me longer to
track down.

--
Jeffrey R. Bailey
"Richard" <rw**********@chello.se> wrote in message
news:G3sub.3792$%W3.19990@amstwist00...
Hi,

I have a form that take some time to load due to many comboboxes and at
least 8 subforms.
When I filter or sort the main form I get an error message and then Access shuts down. They ask if I want to send the error report to Microsoft. Has anybody seen this type of error message and what can I do to prevent it

from
happening. Am I doing something illegal in my code? It used to work but I have added conditional formatting to a subform but that shouldn't cause

any
problem. It ONLY happens when I try to filter or sort the main recordset
using Access built-in functions. I am using Access 2002.
Any help appreciated
Richard


Nov 12 '05 #3
I have 2 controls with conditional formatting. One based on 3 conditions and
the other one on 1 condition. I deleted all figuring I can do this in code.
But the problem persists. Not only when I try to filter but also when I try
to sort the recordset on any control. I have about 1000 records in the
recordset.

Richard
"Jeffrey R. Bailey" <mr**********@yahoo.com> skrev i meddelandet
news:s2***************@twister.tampabay.rr.com...
Incidentally what you are doing isn't illegal and the solution I described
above is only a work around. When I had the problem I searched the news
groups and knowledge bases and never found mention of anyone else having it. I have always assumed it to be an issue related to running multiple
development environments on my main machine. I worked around conditional
formatting by adding some check boxes to reflect the state of the records in a different way. I couldn't do without filtering the main form in my
application.

--
Jeffrey R. Bailey
"Jeffrey R. Bailey" <mr**********@yahoo.com> wrote in message
news:AP***************@twister.tampabay.rr.com...
Conditional formatting in a sub-form and filtering the main form caused this
problem for me, remove the formating and then see if the problem doesn't

go
away. Incidentally, I'll bet that as long as you don't apply a filter to

the
main form the database will work fine even with conditional formatting in
the sub-form. I have had almost exactly the same problem, only in my case Access 2002 would not shut down until I attempted to scroll after

filtering.
You are lucky, because your post contains the cause of this problem and
because mine didn't start until I switched to 2002 it took me longer to
track down.

--
Jeffrey R. Bailey
"Richard" <rw**********@chello.se> wrote in message
news:G3sub.3792$%W3.19990@amstwist00...
Hi,

I have a form that take some time to load due to many comboboxes and at least 8 subforms.
When I filter or sort the main form I get an error message and then Access shuts down. They ask if I want to send the error report to Microsoft. Has anybody seen this type of error message and what can I do to prevent it from
happening. Am I doing something illegal in my code? It used to work
but I have added conditional formatting to a subform but that shouldn't
cause any
problem. It ONLY happens when I try to filter or sort the main

recordset using Access built-in functions. I am using Access 2002.
Any help appreciated
Richard



Nov 12 '05 #4
I was afraid that we were chasing similar symptoms but not the same problem.
Though I discovered how to work around the problem I have the work around
did not lead to any understanding.

To troubleshoot I tried compacting and compiling the database and that
didn't work. I then began removing items (i.e. code(in small blocks, and
only code triggered during startup, or on current), controls, the sub-form,
re-writing queries, etc) from the form until it started to function
normally. Eventually this led to my focusing on the sub-form with
conditional formatting. I discovered that if I removed the sub-form the
main form was Ok. Then it was a matter of isolating the problem on the
sub-form. In order to do this, I re-created the sub-form from scratch, but
without the conditional formatting and that turned out to be the trigger for
my problem. This always struck me as odd, because I was doing no development
on the sub-form. Hopefully, similar steps will eventually lead to your
isolating this problem.

When I describe it like above it seems like a several minute troubleshoot,
but it wasn't. My problem only manifested itself intermittently, and I
could get around it by restoring from an old copy (when I am programming I
make a full back up every hour of my work). I had the luxury of being able
to look at this problem off and on for a month (it only happened on my
machine). I have checked my incident database and the fix that worked for me
was applied on 10-23-03 and since the change the problem has not reappeared.

Sorry I could not offer more help.

--
Jeffrey R. Bailey
"Richard" <rw**********@chello.se> wrote in message
news:g2Gub.3871$%W3.20170@amstwist00...
I have 2 controls with conditional formatting. One based on 3 conditions and the other one on 1 condition. I deleted all figuring I can do this in code. But the problem persists. Not only when I try to filter but also when I try to sort the recordset on any control. I have about 1000 records in the
recordset.

Richard
"Jeffrey R. Bailey" <mr**********@yahoo.com> skrev i meddelandet
news:s2***************@twister.tampabay.rr.com...
Incidentally what you are doing isn't illegal and the solution I described
above is only a work around. When I had the problem I searched the news
groups and knowledge bases and never found mention of anyone else having it.
I have always assumed it to be an issue related to running multiple
development environments on my main machine. I worked around conditional formatting by adding some check boxes to reflect the state of the records in
a different way. I couldn't do without filtering the main form in my
application.

--
Jeffrey R. Bailey
"Jeffrey R. Bailey" <mr**********@yahoo.com> wrote in message
news:AP***************@twister.tampabay.rr.com...
Conditional formatting in a sub-form and filtering the main form caused this
problem for me, remove the formating and then see if the problem
doesn't go
away. Incidentally, I'll bet that as long as you don't apply a filter
to the
main form the database will work fine even with conditional formatting in the sub-form. I have had almost exactly the same problem, only in my case Access 2002 would not shut down until I attempted to scroll after

filtering.
You are lucky, because your post contains the cause of this problem
and because mine didn't start until I switched to 2002 it took me longer to track down.

--
Jeffrey R. Bailey
"Richard" <rw**********@chello.se> wrote in message
news:G3sub.3792$%W3.19990@amstwist00...
> Hi,
>
> I have a form that take some time to load due to many comboboxes and

at > least 8 subforms.
> When I filter or sort the main form I get an error message and then

Access
> shuts down. They ask if I want to send the error report to
Microsoft. Has
> anybody seen this type of error message and what can I do to prevent

it from
> happening. Am I doing something illegal in my code? It used to work but
I
> have added conditional formatting to a subform but that shouldn't

cause any
> problem. It ONLY happens when I try to filter or sort the main recordset > using Access built-in functions. I am using Access 2002.
>
>
> Any help appreciated
>
>
> Richard
>
>
>



Nov 12 '05 #5
The troubleshoot process is the last solution, it's just that I rather not
go into that type of tedious work if I can avoid it. I guess I have to
anyway.

Thanks for all your help,

Richard
"Jeffrey R. Bailey" <mr**********@yahoo.com> skrev i meddelandet
news:sD*****************@twister.tampabay.rr.com.. .
I was afraid that we were chasing similar symptoms but not the same problem. Though I discovered how to work around the problem I have the work around
did not lead to any understanding.

To troubleshoot I tried compacting and compiling the database and that
didn't work. I then began removing items (i.e. code(in small blocks, and
only code triggered during startup, or on current), controls, the sub-form, re-writing queries, etc) from the form until it started to function
normally. Eventually this led to my focusing on the sub-form with
conditional formatting. I discovered that if I removed the sub-form the
main form was Ok. Then it was a matter of isolating the problem on the
sub-form. In order to do this, I re-created the sub-form from scratch, but without the conditional formatting and that turned out to be the trigger for my problem. This always struck me as odd, because I was doing no development on the sub-form. Hopefully, similar steps will eventually lead to your
isolating this problem.

When I describe it like above it seems like a several minute troubleshoot,
but it wasn't. My problem only manifested itself intermittently, and I
could get around it by restoring from an old copy (when I am programming I
make a full back up every hour of my work). I had the luxury of being able to look at this problem off and on for a month (it only happened on my
machine). I have checked my incident database and the fix that worked for me was applied on 10-23-03 and since the change the problem has not reappeared.
Sorry I could not offer more help.

--
Jeffrey R. Bailey
"Richard" <rw**********@chello.se> wrote in message
news:g2Gub.3871$%W3.20170@amstwist00...
I have 2 controls with conditional formatting. One based on 3 conditions and
the other one on 1 condition. I deleted all figuring I can do this in

code.
But the problem persists. Not only when I try to filter but also when I

try
to sort the recordset on any control. I have about 1000 records in the
recordset.

Richard
"Jeffrey R. Bailey" <mr**********@yahoo.com> skrev i meddelandet
news:s2***************@twister.tampabay.rr.com...
Incidentally what you are doing isn't illegal and the solution I described above is only a work around. When I had the problem I searched the news groups and knowledge bases and never found mention of anyone else having
it.
I have always assumed it to be an issue related to running multiple
development environments on my main machine. I worked around conditional formatting by adding some check boxes to reflect the state of the records
in
a different way. I couldn't do without filtering the main form in my
application.

--
Jeffrey R. Bailey
"Jeffrey R. Bailey" <mr**********@yahoo.com> wrote in message
news:AP***************@twister.tampabay.rr.com...
> Conditional formatting in a sub-form and filtering the main form caused this
> problem for me, remove the formating and then see if the problem doesn't go
> away. Incidentally, I'll bet that as long as you don't apply a
filter to the
> main form the database will work fine even with conditional
formatting in
> the sub-form. I have had almost exactly the same problem, only in
my case
> Access 2002 would not shut down until I attempted to scroll after
filtering.
> You are lucky, because your post contains the cause of this problem and > because mine didn't start until I switched to 2002 it took me longer to > track down.
>
> --
> Jeffrey R. Bailey
> "Richard" <rw**********@chello.se> wrote in message
> news:G3sub.3792$%W3.19990@amstwist00...
> > Hi,
> >
> > I have a form that take some time to load due to many comboboxes
and at
> > least 8 subforms.
> > When I filter or sort the main form I get an error message and
then Access
> > shuts down. They ask if I want to send the error report to

Microsoft. Has
> > anybody seen this type of error message and what can I do to

prevent it
> from
> > happening. Am I doing something illegal in my code? It used to
work but
I
> > have added conditional formatting to a subform but that shouldn't

cause
> any
> > problem. It ONLY happens when I try to filter or sort the main

recordset
> > using Access built-in functions. I am using Access 2002.
> >
> >
> > Any help appreciated
> >
> >
> > Richard
> >
> >
> >
>
>
>



Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Nick | last post: by
3 posts views Thread by rdemyan via AccessMonster.com | last post: by
2 posts views Thread by rdemyan via AccessMonster.com | last post: by
27 posts views Thread by didacticone | last post: by
1 post views Thread by gcdp | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.