I have a field AAA with a cross reference index. Why can't I use Btree.Extract on AAA_XREF?

Possible answers:

- Can't be done. Btree.Extract can only be used on normal Btree index

- Can be done with simple workaround

- Should work fine. Must be trivial mistake in your programming!

- Oystein -

[email protected]

Today's listening suggestion:

Spring Heel Jack: Treader (Tugboat Records).

Oystein,

AFAIK:

- Should work fine. Must be trivial mistake in your programming!

[email protected]

SRP Computer Solutions

Don,

Should work fine. Must be trivial mistake in your programming!

Huffda!

But I cannot seem to spot that mistake. Btree.Extract itself isn't very specific about what goes wrong (Flag=-1), but I now tried with a Get_Status which returns the following error status information:

FS211 WEB_0_FOTO MOTIV_XREFÿ271

Hi Oystein,

Check your Stop List on the Xref - There's a bug in OI that thinks having a stop list of null is an error… so if the call to the Xref function in your dictionary record is passing null change it to 1 (use default).

eg if it looks like this

CALL XREF({SEARCH},\20FDFCFB2E2C2D2F\,"","")

change it to this -

CALL XREF({SEARCH},\20FDFCFB2E2C2D2F\,"","1")

Drove me crazy until I found it ( modes of null are fine on Arev 3.12 )

Regards,

[email protected]

Sprezzatura Group

World Leaders in all things RevSoft

Carl,

Thanks for setting me on the right track. I doubt that we had the same problem, but at least you got me to experiment with the XREF formula until I found the cause of the problem.

My cross ref indexes are special because I use more delimiters than Database Manager offers. Often I use my own index creation tool, but this time I used Database Manager. I.e, I used Database Manager to add a cross ref index without immediate build. Then I edited the CALL XREF formula in Table Builder so I got the delimiters I wanted. Sometimes I also changed the stop list and mode parameters. Then I used Database Manager to build (Rebuild) the index.

It seems I can change the CALL XREF formula as much as I want as long as I don't put spaces between the XREF function's parameters. I'm heavily into the habit of having spaces between parameters, but in the XREF formula they obviously created problems this time. Is this a well-known "feature"?

Note. When experimenting with this, I removed the index inbetween each time. If I had a working formula and edited it again without removing the index first, I didn't get the problem. And vice versa. But I guess that makes sense.

Except I'm curious to know exactly where the problem lies.

- Oystein -

View this thread on the forum...