The point? Unnecessary additional complexity not affecting the outcome.
:) My bad.
Although I'm inclined to think that the fact the original poster is
using a SQL query instead of a TCL query might be an indication that
they are not in a position to be creating dictionary items.
Oh, and I
When I do a query is like this:
select table with term eq some term
what I want to do is to
select table within the last 120 or 60 days
All I need is the term within the last 120 days or with in the last 6
months.
The query will be run daily only to capture the lastest information.
I having
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of DG
Sent: 25 October 2006 17:52
To: u2-users@listserver.u2ug.org
Subject: [U2] Query calculating 120 days.
When I do a query is like this:
select table with term eq some term
what I want to do is to
select table within the last 120 or 60
PROTECTED] On Behalf Of DG
Sent: Wednesday, October 25, 2006 12:52 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Query calculating 120 days.
When I do a query is like this:
select table with term eq some term
what I want to do is to
select table within the last 120 or 60 days
All I need
Make a dictionary item for the age of the transaction.
0001 I
0002 DATE()[EMAIL PROTECTED]6
0003
0004 AGE
0005 10R
0006 S
Substitute the attribute number in @RECORD for the transaction date in
your data.
Then you would just:
select table with age le 120 and with term eq some term
HTH,
How about a DATE_AGE I-Type
001: I
002: DATE() - ICONV(*YOUR.DATE.FIELD.HERE*,D4/)
003: MR0
004: DATE AGE
005: 8R
006: S
Karen Bessel wrote:
First of all, you need to determine what date range you're looking for.
In other words what's the first date (120 days ago).
SELECT FILE WITH DATE GE
A couple of points:
Gordon's example: DATE()[EMAIL PROTECTED]6 should really be using a D-type
named field instead of using @RECORDnn
Jeff's example: DATE() - ICONV(*YOUR.DATE.FIELD.HERE*,D4/) - the date
field should already be in internal format, so what's the point of the
ICONV ?
AdrianW
