Another thought
Perhaps you could try
Not > 01/01/1818
So anything that is not a valid date might show up?
Mark
________________________________
From:
vantage@yahoogroups.com [mailto:
vantage@yahoogroups.com] On Behalf
Of Dupuis, Mark
Sent: Wednesday, October 29, 2008 3:40 PM
To:
vantage@yahoogroups.com
Subject: RE: [Vantage] Re: BAQ against Jobhead
Would a null evaluate to less than a specific dumb date like 01/01/1818?
Just a thought.
Mark
________________________________
From:
vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:
vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of corvette6672
Sent: Wednesday, October 29, 2008 3:35 PM
To:
vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: BAQ against Jobhead
I used the phrase builder to create the following, but get no records
returned. If I look at the SQL database, both date fileds are null:
any ideas?
for each JobHead where ( JobHead.JobNum = '0000074' AND
JobHead.TravelerLastPrinted = JobHead.Date10) no-lock .
--- In
vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ,
"Charles Carden" <shadowcar1449@...>
wrote:
>
> Set you criteria to compare the field against a know null date
field such as Date10.
>
> ----- Original Message -----
> From: corvette6672
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
> Sent: Wednesday, October 29, 2008 11:27 AM
> Subject: [Vantage] BAQ against Jobhead
>
>
> Is it possible to deine a BAQ with criteria to select against
records
> that have "null" in the Jobhead.TravelerLastPrinted field?
>
>
>
>
> Charles Carden
> IT Manager
> Manitex, Inc.
>
>
> [Non-text portions of this message have been removed]
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]