Hi
We have a problem with a query.
An Access database links via ODBC to a UNIX server. To speed things, we use
the ODBC to load the relevant tables to the local PC that runs Access so
that all querying is done locally.
One of the reports we run allows the user to list all invoices within a
period. They are also allowed to select a customer code and a product set on
which to base the report. The product set comprises a Warehouse code (a
system grouping classification rather than a physical building) and a
product code. There will always be something in the field [PRODUCT_CODE],
but it is possible for the [WAREHOUSE] field to be null.
We used to run the database in Access 97, and I am pretty sure the following
criteria expression worked, in that if the user hit 'enter' when prompted
for the Warehouse, all records would be returned, including those with
'null' in the [WAREHOUSE] field. About six months ago we converted this
rather large database (c200 queries and reports) to Access 2000. Today, my
users tell me this report is ignoring records that have Warehouse value.
The criteria string used on the [WAREHOUSE] field is as follows
Like [Warehouse or enter for all] & "*"
The variable [Warehouse or enter for all] is then assigned to a created
field of its own, [WAREHOUSE_SELEC TED], to show on the report.
It appears that searching using a wildcard ignores null values, but we need
to be able to pick up the nulls if the user wants all records returned.
Any ideas on how to fix this?
Regards
Tom Millington
6  5257 
Try this criteria expression:
Like [Warehouse or enter for all] & "*" OR [Warehouse or enter for all] Is
Null
--
Ken Snell
<MS ACCESS MVP>
"AAVF" <tm*********@aa vf.co.uk> wrote in message
news:10******** *******@ananke. eclipse.net.uk. .. Hi
We have a problem with a query.
An Access database links via ODBC to a UNIX server. To speed things, we
use the ODBC to load the relevant tables to the local PC that runs Access so
that all querying is done locally.
One of the reports we run allows the user to list all invoices within a
period. They are also allowed to select a customer code and a product set
on which to base the report. The product set comprises a Warehouse code (a
system grouping classification rather than a physical building) and a
product code. There will always be something in the field [PRODUCT_CODE],
but it is possible for the [WAREHOUSE] field to be null.
We used to run the database in Access 97, and I am pretty sure the
following criteria expression worked, in that if the user hit 'enter' when prompted
for the Warehouse, all records would be returned, including those with
'null' in the [WAREHOUSE] field. About six months ago we converted this
rather large database (c200 queries and reports) to Access 2000. Today, my
users tell me this report is ignoring records that have Warehouse value.
The criteria string used on the [WAREHOUSE] field is as follows
Like [Warehouse or enter for all] & "*"
The variable [Warehouse or enter for all] is then assigned to a created
field of its own, [WAREHOUSE_SELEC TED], to show on the report.
It appears that searching using a wildcard ignores null values, but we
need to be able to pick up the nulls if the user wants all records returned.
Any ideas on how to fix this?
Regards
Tom Millington
Thanks Ken
That worked a treat.
Has something changed from A97 to A2000? I'm sure the string I was using
worked on A97.
Tom
"Ken Snell" <kt***********@ notcomcast.real net> wrote in message
news:eH******** ******@TK2MSFTN GP11.phx.gbl... Try this criteria expression:
Like [Warehouse or enter for all] & "*" OR [Warehouse or enter for all] Is
Null
--
Ken Snell
<MS ACCESS MVP>
"AAVF" <tm*********@aa vf.co.uk> wrote in message
news:10******** *******@ananke. eclipse.net.uk. .. Hi
We have a problem with a query.
An Access database links via ODBC to a UNIX server. To speed things, we use the ODBC to load the relevant tables to the local PC that runs Access so
that all querying is done locally.
One of the reports we run allows the user to list all invoices within a
period. They are also allowed to select a customer code and a product
set on which to base the report. The product set comprises a Warehouse code (a
system grouping classification rather than a physical building) and a
product code. There will always be something in the field
[PRODUCT_CODE], but it is possible for the [WAREHOUSE] field to be null.
We used to run the database in Access 97, and I am pretty sure the
following criteria expression worked, in that if the user hit 'enter' when
prompted for the Warehouse, all records would be returned, including those with
'null' in the [WAREHOUSE] field. About six months ago we converted this
rather large database (c200 queries and reports) to Access 2000. Today,
my users tell me this report is ignoring records that have Warehouse value.
The criteria string used on the [WAREHOUSE] field is as follows
Like [Warehouse or enter for all] & "*"
The variable [Warehouse or enter for all] is then assigned to a created
field of its own, [WAREHOUSE_SELEC TED], to show on the report.
It appears that searching using a wildcard ignores null values, but we
need to be able to pick up the nulls if the user wants all records returned.
Any ideas on how to fix this?
Regards
Tom Millington
It shouldn't have UNLESS the fields contained zero-length strings vice null.
Nulls wouldn't match with a wildcard search, but zero-length strings (or a
series of spaces) would.
AAVF IT wrote:
Thanks Ken
That worked a treat.
Has something changed from A97 to A2000? I'm sure the string I was using
worked on A97.
Tom
"Ken Snell" <kt***********@ notcomcast.real net> wrote in message
news:eH******** ******@TK2MSFTN GP11.phx.gbl... Try this criteria expression:
Like [Warehouse or enter for all] & "*" OR [Warehouse or enter for all] Is
Null
--
Ken Snell
<MS ACCESS MVP>
"AAVF" <tm*********@aa vf.co.uk> wrote in message
news:10******** *******@ananke. eclipse.net.uk. .. Hi
We have a problem with a query.
An Access database links via ODBC to a UNIX server. To speed things, we
use the ODBC to load the relevant tables to the local PC that runs Access so
that all querying is done locally.
One of the reports we run allows the user to list all invoices within a
period. They are also allowed to select a customer code and a product set on which to base the report. The product set comprises a Warehouse code (a
system grouping classification rather than a physical building) and a
product code. There will always be something in the field
[PRODUCT_CODE], but it is possible for the [WAREHOUSE] field to be null.
We used to run the database in Access 97, and I am pretty sure the
following criteria expression worked, in that if the user hit 'enter' when prompted for the Warehouse, all records would be returned, including those with
'null' in the [WAREHOUSE] field. About six months ago we converted this
rather large database (c200 queries and reports) to Access 2000. Today, my users tell me this report is ignoring records that have Warehouse value.
The criteria string used on the [WAREHOUSE] field is as follows
Like [Warehouse or enter for all] & "*"
The variable [Warehouse or enter for all] is then assigned to a created
field of its own, [WAREHOUSE_SELEC TED], to show on the report.
It appears that searching using a wildcard ignores null values, but we
need to be able to pick up the nulls if the user wants all records returned.
Any ideas on how to fix this?
Regards
Tom Millington
Thanks for the info.
I am now going through the 400+ queries in this database set to see how many
I have to modify. It looks like about 50.
One thing I have noticed. When I add the extra 'OR' statement to the
criteria and save/exit the query, when I go back into it in design view,
Access has changed the layout so that instead of having one criteria line
with the statement I entered, I now have two: one is the original, with the
'OR' statement on a second ('or') criteria line. I understand the sense in
this. However, some of these queries allow up to six variables to be
selected in the same way, all of which could come back with null-value
fields in the result. This means that when I go back into the query in
design mode, it looks like the query from hell, in that it can have a dozen
or more criteria lines. This means it is going to be a tad difficult to
maintain. Is there any way of getting Access to keep the display as I
entered it, ie one criteria line with statements containing an 'OR'
function?
Regards
Tom
"John Spencer (MVP)" <sp***********@ SPAMNOT.umbc.ed u> wrote in message
news:3F******** *******@SPAMNOT .umbc.edu... It shouldn't have UNLESS the fields contained zero-length strings vice
null. Nulls wouldn't match with a wildcard search, but zero-length strings (or a
series of spaces) would.
AAVF IT wrote:
Thanks Ken
That worked a treat.
Has something changed from A97 to A2000? I'm sure the string I was using
worked on A97.
Tom
"Ken Snell" <kt***********@ notcomcast.real net> wrote in message
news:eH******** ******@TK2MSFTN GP11.phx.gbl... Try this criteria expression:
Like [Warehouse or enter for all] & "*" OR [Warehouse or enter for
all] Is Null
--
Ken Snell
<MS ACCESS MVP>
"AAVF" <tm*********@aa vf.co.uk> wrote in message
news:10******** *******@ananke. eclipse.net.uk. ..
> Hi
>
> We have a problem with a query.
>
> An Access database links via ODBC to a UNIX server. To speed things,
we use
> the ODBC to load the relevant tables to the local PC that runs
Access so > that all querying is done locally.
>
> One of the reports we run allows the user to list all invoices
within a > period. They are also allowed to select a customer code and a
product set on
> which to base the report. The product set comprises a Warehouse code
(a > system grouping classification rather than a physical building) and
a > product code. There will always be something in the field
[PRODUCT_CODE], > but it is possible for the [WAREHOUSE] field to be null.
>
> We used to run the database in Access 97, and I am pretty sure the
following
> criteria expression worked, in that if the user hit 'enter' when
prompted > for the Warehouse, all records would be returned, including those
with > 'null' in the [WAREHOUSE] field. About six months ago we converted
this > rather large database (c200 queries and reports) to Access 2000.
Today, my > users tell me this report is ignoring records that have Warehouse
value. >
> The criteria string used on the [WAREHOUSE] field is as follows
>
> Like [Warehouse or enter for all] & "*"
>
> The variable [Warehouse or enter for all] is then assigned to a
created > field of its own, [WAREHOUSE_SELEC TED], to show on the report.
>
> It appears that searching using a wildcard ignores null values, but
we need
> to be able to pick up the nulls if the user wants all records
returned. >
> Any ideas on how to fix this?
>
> Regards
>
> Tom Millington
>
>
The design view changes that you see are the normal behavior for ACCESS when
you use the Criteria expression that we provided. If you open the query in
SQL, you'll see a similar "jumble".
There is no easy way to maintain this if you want to add more fields with a
similar criterion expression. I usually resort to deleting those fields with
the criteria and recreating them with the "simple" expression.
The alternative is to not use a saved query, and instead build the SQL in
code and then run it.
--
Ken Snell
<MS ACCESS MVP>
"AAVF IT" <it***********@ aavf.co.uk> wrote in message
news:10******** *******@ananke. eclipse.net.uk. .. Thanks for the info.
I am now going through the 400+ queries in this database set to see how
many I have to modify. It looks like about 50.
One thing I have noticed. When I add the extra 'OR' statement to the
criteria and save/exit the query, when I go back into it in design view,
Access has changed the layout so that instead of having one criteria line
with the statement I entered, I now have two: one is the original, with
the 'OR' statement on a second ('or') criteria line. I understand the sense in
this. However, some of these queries allow up to six variables to be
selected in the same way, all of which could come back with null-value
fields in the result. This means that when I go back into the query in
design mode, it looks like the query from hell, in that it can have a
dozen or more criteria lines. This means it is going to be a tad difficult to
maintain. Is there any way of getting Access to keep the display as I
entered it, ie one criteria line with statements containing an 'OR'
function?
Regards
Tom
"John Spencer (MVP)" <sp***********@ SPAMNOT.umbc.ed u> wrote in message
news:3F******** *******@SPAMNOT .umbc.edu... It shouldn't have UNLESS the fields contained zero-length strings vice null. Nulls wouldn't match with a wildcard search, but zero-length strings (or
a series of spaces) would.
AAVF IT wrote:
Thanks Ken
That worked a treat.
Has something changed from A97 to A2000? I'm sure the string I was
using worked on A97.
Tom
"Ken Snell" <kt***********@ notcomcast.real net> wrote in message
news:eH******** ******@TK2MSFTN GP11.phx.gbl...
> Try this criteria expression:
>
> Like [Warehouse or enter for all] & "*" OR [Warehouse or enter for
all] Is > Null
>
> --
> Ken Snell
> <MS ACCESS MVP>
>
> "AAVF" <tm*********@aa vf.co.uk> wrote in message
> news:10******** *******@ananke. eclipse.net.uk. ..
> > Hi
> >
> > We have a problem with a query.
> >
> > An Access database links via ODBC to a UNIX server. To speed
things, we > use
> > the ODBC to load the relevant tables to the local PC that runs Access so > > that all querying is done locally.
> >
> > One of the reports we run allows the user to list all invoices within a > > period. They are also allowed to select a customer code and a product set
> on
> > which to base the report. The product set comprises a Warehouse
code (a > > system grouping classification rather than a physical building)
and a > > product code. There will always be something in the field
[PRODUCT_CODE],
> > but it is possible for the [WAREHOUSE] field to be null.
> >
> > We used to run the database in Access 97, and I am pretty sure the
> following
> > criteria expression worked, in that if the user hit 'enter' when
prompted
> > for the Warehouse, all records would be returned, including those with > > 'null' in the [WAREHOUSE] field. About six months ago we converted this > > rather large database (c200 queries and reports) to Access 2000. Today, my
> > users tell me this report is ignoring records that have Warehouse value. > >
> > The criteria string used on the [WAREHOUSE] field is as follows
> >
> > Like [Warehouse or enter for all] & "*"
> >
> > The variable [Warehouse or enter for all] is then assigned to a created > > field of its own, [WAREHOUSE_SELEC TED], to show on the report.
> >
> > It appears that searching using a wildcard ignores null values,
but we > need
> > to be able to pick up the nulls if the user wants all records returned. > >
> > Any ideas on how to fix this?
> >
> > Regards
> >
> > Tom Millington
> >
> >
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Shabam |
last post by:
A web application of mine developed using C# + MS SQL runs fine normally.
However when I stress test it with a load testing software (using about 60
simultaneous users) some instances start erroring out. I see two different
errors. One is a "Object reference not set to an instance of an object."
error, which appears to always contain the...
|
by: neptune |
last post by:
I have a query where each customer has an or . Sometimes
both fields for a customer are populated, but if is null, then
will be populated and vice versa. I have a form,
, where I select a value for from a combo
box. In my query I set the criteria for to
... My query finds the proper values
for .
Now I also want to find the values...
|
by: JM |
last post by:
Hello,
I've created a Querydef in a Form_Load() sub. The form is a subform
that no longer has linked child fields. The form is bound to this
querydef. When I open the form, the fields are populated just fine.
However, when I add a new record using the new record control at the
bottom of the subform, it gets added with NULL for the two...
|
by: LFM |
last post by:
I have a table called "employee profile" which contains a bunch of user
information. In that table I have a field called "Description" which is a
text/memo field. This field is not mandetory to be filled in, so in many
cases the field contains a null value.
I would like to create a query that lists all the records that do not
contain the...
|
by: Mark Roughton |
last post by:
I have a form where the users need to view records for various
criteria, one of which is a date field on which they may wish to view
all related data for the selected date, for all dates upto and icluding
the selected date or all records on or after the selected date
The user selects either "=", >=" or "<=" from a combo box and then a
date...
| | |
by: Ragbrai |
last post by:
Howdy All,
I have a query that is used for filtering results to be used in a combo box. The query needs to test fields from both a table and then unbound text boxes on the form that also contains the combo box. The fields I am working with are date fields that are formated as Short Date. I have written an IIF statement and placed it within the...
|
by: WU10 |
last post by:
Built a form based on a select query with a combo box (3 choices) in
the form header which will supply a value to the query. In the
query's criteria I added the following expression - !!
and this works like a charm. However one of my users wanted
to see all of the values before choosing one of the three
selections.
I added the choice...
|
by: seagullino |
last post by:
Hello,
I've developed my first Form, a simple affair that enables the user to search text in the memo fields in our database. When the "search" button is pressed, it runs a macro which runs the simple query.
I have added a second field to the form, in addition to the text search field. This new field allows the user to type in an...
|
by: Dr Al |
last post by:
I have a table with four date fields, some of which may not be filled
in based on our data entry needs. I have a criteria set as <date()-180
which is supposed to pull dates older than 180 days ago. The problem
is that when I use that criteria for all four fields I am not getting
the expected results.
I am trying to find out from this query...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language...
| | |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| | |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating...
| |
