G
GlennH
I'm following an article "Working with groups of records
using marcos" which is an excerpt from the book MS Acess
2002 Prem Ed by Robinson & Simpson. I got it off the web
from a now unknown Access info/forum. I'm interested in
the article following on from "Creating a filter query"
The article describes a filter query based on the same
query the form is based on. A combo box to hold the
search variable and a macro to trigger the combo's
AfterUpdate event to run ApplyFilter and display the
appropriate records.
I've got Customer, Suburb, Postcode and some other fields
(12 in total) from the base query and set the criteria
all the same way. For CustomerName - "Forms!frmOrders!
cboCustomer OR Forms!frmOrders!cboCustomer IS NULL"
Everything in line with the article. Sorry, I don't know
how to give you more info to help me without actually
posting the whole article. Anyone who can help and wants
to see the article, yell out..
Anyway, the whole thing works fine! I can't fault it. But
I can't go into the query in design view without
apparently corrupting the query. If I do open it in
design view,
when run the query doesn't work;
my processor is tied up 100% for eternity
when I do get a look at it, in SQL view the statement
is about a mile long
Interestingly, if I only have the first 3 or 4 fields in
the query, I can view/edit the query in design view - so
is there a limit to the SQL length? But why does it work
whilst left alone.
I wonder if I am doing everything OK, except that I have
more fields than was anticipated by the article.
This process runs OK in my project at work, but I'm not
happy with the uncertainty of maintaining the query and
database. This is the second time I have visited this
article and process (1st, 12 months ago). Same then, and
I abandoned it. But it has merits that I can apply to my
application and work like to resolve the perceived
problem - or consider any alternatives??
Regards
GlennH
using marcos" which is an excerpt from the book MS Acess
2002 Prem Ed by Robinson & Simpson. I got it off the web
from a now unknown Access info/forum. I'm interested in
the article following on from "Creating a filter query"
The article describes a filter query based on the same
query the form is based on. A combo box to hold the
search variable and a macro to trigger the combo's
AfterUpdate event to run ApplyFilter and display the
appropriate records.
I've got Customer, Suburb, Postcode and some other fields
(12 in total) from the base query and set the criteria
all the same way. For CustomerName - "Forms!frmOrders!
cboCustomer OR Forms!frmOrders!cboCustomer IS NULL"
Everything in line with the article. Sorry, I don't know
how to give you more info to help me without actually
posting the whole article. Anyone who can help and wants
to see the article, yell out..
Anyway, the whole thing works fine! I can't fault it. But
I can't go into the query in design view without
apparently corrupting the query. If I do open it in
design view,
when run the query doesn't work;
my processor is tied up 100% for eternity
when I do get a look at it, in SQL view the statement
is about a mile long
Interestingly, if I only have the first 3 or 4 fields in
the query, I can view/edit the query in design view - so
is there a limit to the SQL length? But why does it work
whilst left alone.
I wonder if I am doing everything OK, except that I have
more fields than was anticipated by the article.
This process runs OK in my project at work, but I'm not
happy with the uncertainty of maintaining the query and
database. This is the second time I have visited this
article and process (1st, 12 months ago). Same then, and
I abandoned it. But it has merits that I can apply to my
application and work like to resolve the perceived
problem - or consider any alternatives??
Regards
GlennH