Try using NO.INDEX and see if you get the results you are looking for. If
that is the case, you need to rebuild the index. Have you had any system
crashes lately?
select ORDERS NO.INDEX WITH CUST.NO = '12345' AND WITH INV.DATE =
'12/14/05'
-Original Message-
From: [EMAIL PROTECTED]
It's always been my understanding that the single quotes don't work at
ECL/TCL. I'd try the same thing but use double quotes instead.
Gordon J. Glorfield
Sr. Applications Developer
UnitedHealthcare's Mid-Atlantic Health Plans
301-360-8839
[EMAIL PROTECTED] wrote on 08/29/2006 09:53:33 AM:
No system crashes. It's a brand new file that I created.
001: D
002: 1
003: D4-
004: Inv Date
005: 8L
006: S
001: V
002: SUBR(-OCONVS,@ID,G0.1)
003:
When we execute at TCL SELECT ORDERS WITH CUST.NO = '12345' AND WITH
INV.DATE = '12/14/05' no items are selected.
And if you disable the index (via DISABLE.INDEX) the select works
fine? And is the customer number and invoice date both in the ORDERS
file?
-Kevin
[EMAIL PROTECTED]
OK, I'll ask the obvious question. Are you sure that there is data
matching this criteria in the file?
Dave S wrote:
We have a file that has the customer number and invoice date indexed.
When we execute at TCL SELECT ORDERS WITH CUST.NO = '12345' AND WITH INV.DATE = '12/14/05' no items
If you have the luxury and can do a build.index on primetime then do it.
This would rule out corrupted indexes.
Hope It helps.
Cheers,
Angelo
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dave S
Sent: Tuesday, August 29, 2006 9:54 AM
To:
[EMAIL PROTECTED] wrote on 08/29/2006 09:53:33 AM:
When we execute at TCL SELECT ORDERS WITH CUST.NO = '12345' AND
WITH INV.DATE = '12/14/05' no items are selected.
Try it with double quotes instead of single quotes. It may be taking those
values as primary keys.
---
u2-users mailing
Dave,
I'm not aware of any issues.
UniData will only use one index per Select statement.
What results do you get when you use the NO.INDEX keyword?
Thanks,
David A. Green
DAG Consulting
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave S
Sent:
We have tried both ways.
I am now tweaking the invoice date dictionary to see if that helps.
Gordon J Glorfield [EMAIL PROTECTED] wrote:
It's always been my understanding that the single quotes don't work at
ECL/TCL. I'd try the same thing but use double quotes instead.
Gordon J.
We had a problem with the udtsort.exe in 5.2. IBM actually had us use
the udtsort.exe from an earlier version. Now that I think about it, the
problem may not have been resolved until 6.0.12. Please don't start
using different versions of udtsort.exe without verification from IBM of
which versions
Yes. I am sure.
If for some reason, I can't get this index to work --- I may convert the date
to output
format and store it that way.
Jeff Schasny [EMAIL PROTECTED] wrote:
OK, I'll ask the obvious question. Are you sure that there is data
matching this criteria in the file?
Dave S
If the indexes are deleted, the select statement works fine.
Kevin King [EMAIL PROTECTED] wrote:
When we execute at TCL SELECT ORDERS WITH CUST.NO = '12345' AND WITH
INV.DATE = '12/14/05' no items are selected.
And if you disable the index (via DISABLE.INDEX) the select works
fine? And
I have done so.
Angelo Collazo [EMAIL PROTECTED] wrote: If you have the luxury and can do a
build.index on primetime then do it.
This would rule out corrupted indexes.
Hope It helps.
Cheers,
Angelo
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dave S
OK. I am using double-quotes at TCL.
Timothy Snyder [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote on
08/29/2006 09:53:33 AM:
When we execute at TCL SELECT ORDERS WITH CUST.NO = '12345' AND
WITH INV.DATE = '12/14/05' no items are selected.
Try it with double quotes instead of single
If you do multiple selects does it work?
SELECT ORDERS WITH CUST.NO = '12345'
xx items selected
SELECT ORDERS WITH INV.DATE = '12/14/05'
Richard
We have a file that has the customer number and invoice date indexed.
When we execute at TCL SELECT ORDERS WITH CUST.NO = '12345' AND WITH
Yes. I do recall having a problem with a Unidata release years ago. After
struggling with the release for several months. IBM finally admitted that they
had a major
bug in that release.
[EMAIL PROTECTED] wrote:
We had a problem with the udtsort.exe in 5.2. IBM actually had us use
the
I will need to check in the morning. But I am almost certain that it
does work this way.
Richard Brown [EMAIL PROTECTED] wrote:
If you do multiple selects does it work?
SELECT ORDERS WITH CUST.NO = '12345'
xx items selected
SELECT ORDERS WITH INV.DATE = '12/14/05'
Richard
We have a
17 matches
Mail list logo
