Re: [U2] Running Account wide I-DESC
Depending on the complexity of the I-type, you can sometimes accomplish the same thing with an S-type, which is not compiled. So we use that sometimes for global type dictionary items like that. So for example we put an item COUNTER in the VOC which we can use on any file: COUNTER 0001 S 0002 0 0003 0004 0005 0006 0007 0008 A;1 0009 R 0010 5 -Dianne On 12/5/2013 3:44 PM, George Gallen wrote: Not sure if this helps anyone... There is an I DESC that we usually put in the DICT of most files. Usually, when you go to use it, it hadn't been entered, while not difficult to enter - just a pain. I tried to put the IDESC in VOC, but I wasn't able to compile it I was able to put it in the VOC of VOC - which compiled - but wasn't usable globally. SoIn order to get an IDESC to be used globally (at least globally within that account). You must... 1. Enter the IDESC into the VOC of VOC 2. Compile the IDESC 3. COPY from the VOC VOC to VOC Now it's usable on any file without having to add it Funny, if you want to add a D type DICT , you only need to put it in VOC, But , with I DESC, the problem is compiling it - you can only compile in the VOC of VOC Then you have to copy it into VOC for it to be usable. Like I said...If it helps...great, If not - move on. George George Gallen Senior Programmer/Analyst Accounting/Data Division, EDI Administrator ggal...@wyanokegroup.com ph:856.848.9005 Ext 220 The Wyanoke Group http://www.wyanokegroup.comhttp://www.wyanokegroup.com/ ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] Unidata index/query ?
Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: File.. H08.CR.COURSE.EVALS Alternate key length.. 20 Node/Block size... 4K OV blocks. 1 (0 in use, 0 overflowed) Indices... 6 (6 D-type) Index updates. Enabled, No updates pending Index-Name.. F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr XCCE.STUDENT.ID D NumYes Yes Yes Yes S 8 XCCE.STATUS D TxtYes No Yes Yes S 17 XCCE.COURSE.NAME D TxtYes No Yes Yes S 14 XCCE.TERM D TxtYes No Yes Yes S 12 XCCE.TYPE D TxtYes No Yes Yes S 22 XCCE.SUBJECT D TxtYes No Yes Yes S 23 Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata index/query ?
On 06/12/13 15:08, jeffrey Butera wrote: Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. Can't speak for UniData, but on *older* versions of UV, this is what would be expected. UV only used one index, and even if further select fields were indexed it would run a full scan of the records selected by the first index. However, this was fixed in UV quite a long time ago. I'd be surprised if it wasn't fixed in modern UD too, either. If you're just doing a select, then I'd try the following (dunno if it's available in UD, don't know the exact correct syntax for UV) SELECT WITH TERM EQ 2013F TO 1 SELECT WITH TYPE EQ FINCRSE TO 2 SELECT INTERSECT 1 2 TO 0 Does that take 10 seconds? Something's bizarrely wrong if so. The other thing, does SELECT have an explain clause that'll tell you what it's doing? If none of this works, just create an i-descriptor of the two fields concatenated, and select on that. Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata index/query ?
Jeffrey, And index is a B(Binary)+ tree, the plus means that it auto adjusts and balances itself as it builds or shrinks. After UniData 5.2 UniQuery will use as many indices as it can. In your case it is the equivalent of doing two UniQuery selects to two different lists and then doing a MERGE.LIST. If you are always wanting a combined index lookup on those two values you can create an I-Descriptor that combines them and index the I-Descriptor. Then use the I-Descriptor in your select statements. Remember using an Index doesn't always mean faster selects. If your index brings back a lot of records then you are processing them by index pointer and the disk reads will be all over the file. Whereas without the index you are reading the file going through it by groups and it will minimize the disk reads. David A. Green (480) 201-7953 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera Sent: Friday, December 06, 2013 8:09 AM To: U2 Users List Subject: [U2] Unidata index/query ? Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: File.. H08.CR.COURSE.EVALS Alternate key length.. 20 Node/Block size... 4K OV blocks. 1 (0 in use, 0 overflowed) Indices... 6 (6 D-type) Index updates. Enabled, No updates pending Index-Name.. F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr XCCE.STUDENT.ID D NumYes Yes Yes Yes S 8 XCCE.STATUS D TxtYes No Yes Yes S 17 XCCE.COURSE.NAME D TxtYes No Yes Yes S 14 XCCE.TERM D TxtYes No Yes Yes S 12 XCCE.TYPE D TxtYes No Yes Yes S 22 XCCE.SUBJECT D TxtYes No Yes Yes S 23 Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata index/query ?
Hi David: In Unidata indexes DO mean faster selects. I have file with millions of records with about 14 indexes and most every select on the index comes back in under a second. Our disks are 90,000 IO's per second with a 16GB main memory, without indexes to select and read through that data takes 5 to 10 minutes minimum. I have an open ticket with Rocket Software about indexes failing after 7.3.2. I had a similar problem and reduced my version from 7.3.4 to 7.3.2. Regards, Doug www.u2logic.com XLr8Tools for Universe and Unidata programmers On Fri, Dec 6, 2013 at 9:00 AM, David A. Green dgr...@dagconsulting.com wrote: Jeffrey, And index is a B(Binary)+ tree, the plus means that it auto adjusts and balances itself as it builds or shrinks. After UniData 5.2 UniQuery will use as many indices as it can. In your case it is the equivalent of doing two UniQuery selects to two different lists and then doing a MERGE.LIST. If you are always wanting a combined index lookup on those two values you can create an I-Descriptor that combines them and index the I-Descriptor. Then use the I-Descriptor in your select statements. Remember using an Index doesn't always mean faster selects. If your index brings back a lot of records then you are processing them by index pointer and the disk reads will be all over the file. Whereas without the index you are reading the file going through it by groups and it will minimize the disk reads. David A. Green (480) 201-7953 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera Sent: Friday, December 06, 2013 8:09 AM To: U2 Users List Subject: [U2] Unidata index/query ? Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: File.. H08.CR.COURSE.EVALS Alternate key length.. 20 Node/Block size... 4K OV blocks. 1 (0 in use, 0 overflowed) Indices... 6 (6 D-type) Index updates. Enabled, No updates pending Index-Name.. F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr XCCE.STUDENT.ID D NumYes Yes Yes Yes S 8 XCCE.STATUS D TxtYes No Yes Yes S 17 XCCE.COURSE.NAME D TxtYes No Yes Yes S 14 XCCE.TERM D TxtYes No Yes Yes S 12 XCCE.TYPE D TxtYes No Yes Yes S 22 XCCE.SUBJECT D TxtYes No Yes Yes S 23 Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata index/query ?
In Unidata indexes DO mean faster selects. I have file with millions of records with about 14 indexes and most every select on the index comes back in under a second. Our disks are 90,000 IO's per second with a 16GB main memory, without indexes to select and read through that data takes 5 to 10 minutes minimum. I have an open ticket with Rocket Software about indexes failing after 7.3.2. I had a similar problem and reduced my version from 7.3.4 to 7.3.2. Regards, Doug www.u2logic.com XLr8Tools for Universe and Unidata programmers On Fri, Dec 6, 2013 at 9:00 AM, David A. Green dgr...@dagconsulting.com wrote: Jeffrey, And index is a B(Binary)+ tree, the plus means that it auto adjusts and balances itself as it builds or shrinks. After UniData 5.2 UniQuery will use as many indices as it can. In your case it is the equivalent of doing two UniQuery selects to two different lists and then doing a MERGE.LIST. If you are always wanting a combined index lookup on those two values you can create an I-Descriptor that combines them and index the I-Descriptor. Then use the I-Descriptor in your select statements. Remember using an Index doesn't always mean faster selects. If your index brings back a lot of records then you are processing them by index pointer and the disk reads will be all over the file. Whereas without the index you are reading the file going through it by groups and it will minimize the disk reads. David A. Green (480) 201-7953 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera Sent: Friday, December 06, 2013 8:09 AM To: U2 Users List Subject: [U2] Unidata index/query ? Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: File.. H08.CR.COURSE.EVALS Alternate key length.. 20 Node/Block size... 4K OV blocks. 1 (0 in use, 0 overflowed) Indices... 6 (6 D-type) Index updates. Enabled, No updates pending Index-Name.. F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr XCCE.STUDENT.ID D NumYes Yes Yes Yes S 8 XCCE.STATUS D TxtYes No Yes Yes S 17 XCCE.COURSE.NAME D TxtYes No Yes Yes S 14 XCCE.TERM D TxtYes No Yes Yes S 12 XCCE.TYPE D TxtYes No Yes Yes S 22 XCCE.SUBJECT D TxtYes No Yes Yes S 23 Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata index/query ?
Yes, Doug if an index is properly done it will make a huge difference. But there are times when using an index can be slower. And this is the point I'm making. David A. Green (480) 201-7953 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Doug Averch Sent: Friday, December 06, 2013 9:13 AM To: U2 Users List Subject: Re: [U2] Unidata index/query ? Hi David: In Unidata indexes DO mean faster selects. I have file with millions of records with about 14 indexes and most every select on the index comes back in under a second. Our disks are 90,000 IO's per second with a 16GB main memory, without indexes to select and read through that data takes 5 to 10 minutes minimum. I have an open ticket with Rocket Software about indexes failing after 7.3.2. I had a similar problem and reduced my version from 7.3.4 to 7.3.2. Regards, Doug www.u2logic.com XLr8Tools for Universe and Unidata programmers On Fri, Dec 6, 2013 at 9:00 AM, David A. Green dgr...@dagconsulting.com wrote: Jeffrey, And index is a B(Binary)+ tree, the plus means that it auto adjusts and balances itself as it builds or shrinks. After UniData 5.2 UniQuery will use as many indices as it can. In your case it is the equivalent of doing two UniQuery selects to two different lists and then doing a MERGE.LIST. If you are always wanting a combined index lookup on those two values you can create an I-Descriptor that combines them and index the I-Descriptor. Then use the I-Descriptor in your select statements. Remember using an Index doesn't always mean faster selects. If your index brings back a lot of records then you are processing them by index pointer and the disk reads will be all over the file. Whereas without the index you are reading the file going through it by groups and it will minimize the disk reads. David A. Green (480) 201-7953 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera Sent: Friday, December 06, 2013 8:09 AM To: U2 Users List Subject: [U2] Unidata index/query ? Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: File.. H08.CR.COURSE.EVALS Alternate key length.. 20 Node/Block size... 4K OV blocks. 1 (0 in use, 0 overflowed) Indices... 6 (6 D-type) Index updates. Enabled, No updates pending Index-Name.. F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr XCCE.STUDENT.ID D NumYes Yes Yes Yes S 8 XCCE.STATUS D TxtYes No Yes Yes S 17 XCCE.COURSE.NAME D TxtYes No Yes Yes S 14 XCCE.TERM D TxtYes No Yes Yes S 12 XCCE.TYPE D TxtYes No Yes Yes S 22 XCCE.SUBJECT D TxtYes No Yes Yes S 23 Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Running Account wide I-DESC
you only need to do this on universe. unidata is happy to use itypes without having them compiled first. universe's CD command insists on only working on the dict. It would be nice if it accepted the DICT/DATA keywords: CD DATA VOC IDESC On Dec 5, 2013, at 3:44 PM, George Gallen ggal...@wyanokegroup.com wrote: Not sure if this helps anyone... There is an I DESC that we usually put in the DICT of most files. Usually, when you go to use it, it hadn't been entered, while not difficult to enter - just a pain. I tried to put the IDESC in VOC, but I wasn't able to compile it I was able to put it in the VOC of VOC - which compiled - but wasn't usable globally. SoIn order to get an IDESC to be used globally (at least globally within that account). You must... 1. Enter the IDESC into the VOC of VOC 2. Compile the IDESC 3. COPY from the VOC VOC to VOC Now it's usable on any file without having to add it Funny, if you want to add a D type DICT , you only need to put it in VOC, But , with I DESC, the problem is compiling it - you can only compile in the VOC of VOC Then you have to copy it into VOC for it to be usable. Like I said...If it helps...great, If not - move on. George George Gallen Senior Programmer/Analyst Accounting/Data Division, EDI Administrator ggal...@wyanokegroup.com ph:856.848.9005 Ext 220 The Wyanoke Group http://www.wyanokegroup.comhttp://www.wyanokegroup.com/ ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata error for the ages, so to speak.
Doug: This is a UniData anomaly. You can't reference fields like @RECORD3, you have to refer to them like EXTRACT(@RECORD,3,0,0). HTH, Bill Untitled Page - Original Message - *From:* dave...@gmail.com *To:* U2 Users List u2-users@listserver.u2ug.org *Date:* 12/5/2013 1:44 PM *Subject:* [U2] Unidata error for the ages, so to speak. I was playing with EVAL trying to see why it would work in Universe and not in Unidata. I typed in this sentence in Unidata 7.3.6: list CRM.CUSTOMERS WITH EVAL UPCASE(@RECORD15) LIKE BILL... UPCASE(@RECORD15) -^ Virtual Attribute Error: qz1zq syntax error So what is qz1zq syntax error? Who would of thought this would help a seasoned professional like myself figure our my syntax error. I guess I really don't understand this database after many many years... The correct syntax was : list CRM.CUSTOMERS WITH EVAL UPCASE(CONTACT.NAME) LIKE 'BILL...' Regards, Doug www.u2logic.com Web applications with real error messages ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Running Account wide I-DESC
Doesn't UV have a DICT.DICT ? In UD you can create truly global dictionaries by placing them in DICT.DICT. Bill - Original Message - *From:* dia...@aptron.com *To:* U2 Users List u2-users@listserver.u2ug.org *Date:* 12/6/2013 6:13 AM *Subject:* Re: [U2] Running Account wide I-DESC Depending on the complexity of the I-type, you can sometimes accomplish the same thing with an S-type, which is not compiled. So we use that sometimes for global type dictionary items like that. So for example we put an item COUNTER in the VOC which we can use on any file: COUNTER 0001 S 0002 0 0003 0004 0005 0006 0007 0008 A;1 0009 R 0010 5 -Dianne On 12/5/2013 3:44 PM, George Gallen wrote: Not sure if this helps anyone... There is an I DESC that we usually put in the DICT of most files. Usually, when you go to use it, it hadn't been entered, while not difficult to enter - just a pain. I tried to put the IDESC in VOC, but I wasn't able to compile it I was able to put it in the VOC of VOC - which compiled - but wasn't usable globally. SoIn order to get an IDESC to be used globally (at least globally within that account). You must... 1. Enter the IDESC into the VOC of VOC 2. Compile the IDESC 3. COPY from the VOC VOC to VOC Now it's usable on any file without having to add it Funny, if you want to add a D type DICT , you only need to put it in VOC, But , with I DESC, the problem is compiling it - you can only compile in the VOC of VOC Then you have to copy it into VOC for it to be usable. Like I said...If it helps...great, If not - move on. George George Gallen Senior Programmer/Analyst Accounting/Data Division, EDI Administrator ggal...@wyanokegroup.com ph:856.848.9005 Ext 220 The Wyanoke Group http://www.wyanokegroup.comhttp://www.wyanokegroup.com/ ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata index/query ?
Maybe I am just old school but I would put another WITH in the line after the AND. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera Sent: Friday, December 06, 2013 7:09 AM To: U2 Users List Subject: [U2] Unidata index/query ? Unidata 7.3.3 on RedHat: I have a table with numerous indicies built: File.. H08.CR.COURSE.EVALS Alternate key length.. 20 Node/Block size... 4K OV blocks. 1 (0 in use, 0 overflowed) Indices... 6 (6 D-type) Index updates. Enabled, No updates pending Index-Name.. F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr XCCE.STUDENT.ID D NumYes Yes Yes Yes S 8 XCCE.STATUS D TxtYes No Yes Yes S 17 XCCE.COURSE.NAME D TxtYes No Yes Yes S 14 XCCE.TERM D TxtYes No Yes Yes S 12 XCCE.TYPE D TxtYes No Yes Yes S 22 XCCE.SUBJECT D TxtYes No Yes Yes S 23 Since these are data fields (nothing computed on-the-fly) and indexed, queries should be fast.The table has approximately 737,000 records. This query runs in under 1 second: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' However this query takes 10+ seconds (or longer) - even with two indexed fields: SELECT H08.CR.COURSE.EVALS WITH XCCE.TERM EQ '2013F' AND XCCE.TYPE EQ 'FINCRSE' I'm at a loss to explain the second, any insight appreciated. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
