btree.xtract strange error (OpenInsight 32-bit Specific)
At 27 MAR 2003 07:35:01PM Bob Watson wrote:
I have an error occuring when I call btree.extract on any xref index with the word "associates" as the last search value. Could someone tell me if this code works againt ANY XRef index
open 'DICT.NOTES' to hDict else return
keys='
str=SUBJECT_XREF' :@vm: "jones" :@vm: "associates" : @fm
btree.extract(str, "NOTES", hDict, keys, 'S', flag)
The error is
Btree.Extract internal error: "SET_OR: ActiveSets=1" Thanks
Bob Watson
At 27 MAR 2003 11:22PM Barry Stevens wrote:
YES…get error here v4.1.2 & V4.1.3
At 27 MAR 2003 11:32PM Barry Stevens wrote:
A non _XREF field works OK.
At 28 MAR 2003 12:53AM Bob Watson wrote:
Thanks Barry - we've found OI obscure bug no. 17! - Revtech please note.
Bob Watson
At 28 MAR 2003 01:43AM Donald Bakke wrote:
Bob,
I'm curious, did you remove ASSOCIATES out of the XREF Stoplist before building your index?
dbakke@srpcs.com
At 28 MAR 2003 04:40AM Oystein Reigem wrote:
Bob,
Like Don I immediately thought of stop words when I saw the word "associates". Possibly unlike him I can't see why it has anything to do with the problem. But if it can be of any relief I can report that I have no problem with your Btree.Extract search criteria here in my totally stop word-less 4.1.2 cross ref indexes.
Personally I can only see disadvantages with using stop words. I don't think Database Manager should use stop words as default when making cross ref indexes. That's one reason I use my own tool to make indexes. (A more important reason is that I can have my own set of delimiters for xrefs. Database Manager's list simply doesn't contain all the characters my clients regard as word delimiters.)
- Oystein -
At 28 MAR 2003 06:18AM Bob Watson wrote:
No I didn't - but even if I did it doesn't explain btree.extract crashing does it?
If the word 'associates' is the first search value it works fine by the way.
Bob Watson
At 28 MAR 2003 06:22AM Bob Watson wrote:
Oystein
It's interesting that you have no problem without stop words but Barry and I have a problem with them. I will try removing the word 'associates' and test it with other words in stop list - maybe it has something to do with it.
Bob Watson
At 28 MAR 2003 06:41AM Oystein Reigem wrote:
Bob,
Have you got any real reason to continue using stop words?
I said my system is without stop words. To be more precise: My app's ENV row still contains the standard Revelation stop word list. (Except for some reason the words are in a different order.) I just don't use a list when I build cross ref indexes. I do it programmatically with
Create_Index( "2", TableName, FieldName, "0", "0", MyOwnXREFDelimiterList, "3" ), "3" meaning I use my own, empty stop word list, i.e, no stop words. (And as you know, also in Database Manager one can build cross ref indexes without stop words.)
- Oystein -