Re: access crashing after filter
- From: "riyaz.mansoor@xxxxxxxxx" <riyaz.mansoor@xxxxxxxxx>
- Date: 9 May 2007 20:13:52 -0700
On May 9, 4:43 pm, "BruceM" <bam...@xxxxxxxxxxxxxxxxx> wrote:
It isn't so much a case of not understanding as not knowing you are using
SQL server and an ADO recordset. Maybe I should have known that from the
code, but I didn't. It seems you are saying that tRst.Filter = "my filter"
results in the recordset tRst being redefined as a filtered recordset, so
that in the line Set Me.Recordset = tRst, Me.Recordset is now the filtered
recordset without specifically applying the filter.
My comments about error handling still apply. If you use error handling in
the procedure (or maybe set the code to break on all errors) you should be
able to find out what error is causing the crash. If the code isn't
reaching your Debug.Print line, why not try putting a Debug.Print line
elsewhere, such as before the line that is causing the crash to see if tRst
is what you expect?
from my second post.
successfullySet Me.Recordset = tRst 'Crash here after Form_Current completes
Debug.Print tRst.RecordCount
Also of note. When the crash message is displayed the form has
CORRECTLY updated to reflect the filtered results. Hence, it appears
its a problem inherent in Access.
I have already given up on this approach with Access
Riyaz
.
- Follow-Ups:
- Re: access crashing after filter
- From: BruceM
- Re: access crashing after filter
- References:
- access crashing after filter
- From: riyaz.mansoor@xxxxxxxxx
- Re: access crashing after filter
- From: riyaz.mansoor@xxxxxxxxx
- Re: access crashing after filter
- From: BruceM
- Re: access crashing after filter
- From: riyaz.mansoor@xxxxxxxxx
- Re: access crashing after filter
- From: BruceM
- access crashing after filter
- Prev by Date: Re: PopUp Form is blank white
- Next by Date: Re: Subform within a subform - filtering problems
- Previous by thread: Re: access crashing after filter
- Next by thread: Re: access crashing after filter
- Index(es):
Relevant Pages
|
Loading