I am in the process of building a Runtime to deploy on the network from the PC where I have been doing development work. Everything has gone well apparently but there is one horrible consequence. If I go to Application Manager Database columns. There is now an additional suffix |S1u(umlaut) P on each database column. This looks critical. ? like a sort that?s stopped halfway through. Can I get rid of them or do I do a restore. If I do a restore how can I stop this happening again as this is the second time it has happened.

Any ideas anyone?

Looks like a phantom index from the original Arev Table. Has now completed successfully. Is there a check list for RX101 errors available?

John,

Check list? As in a list of possible causes for RIX101? Do a search. Start at .

- Oystein -

Thankyou Oystein. There does not seem to be much information but for what its worth I have found the following:

1. Prefixing a Table with SYS - Nothing to prevent this just trouble and strife until you find that part of the manual.

2. Phantom Indexes when using old Arev Tables, even though you believe all indexes had been deleted beforehand.

3. Orphaned GarbageCollect Tables.

4. Tables seem to like more than one Dictionary Definition, not just the Id.

5. Corrupted DBT File

Any others?

John,

Reasons for RIX101: You didn't mention international collation sequence with =@SVM in it. . Might be a bit exotic for you.

- Oystein -

Thanks Oystein. Not at all, was working in Warsaw last year, though not with OI. Correction to earlier Tables should be DUMP_FIX_GARBAGE and DUMP_FIX_TEMP

I have found that if I synchronise the database before I rebuild system Indexes then I don't get these rx101 errors. Can we have more elaborate messaging when these errors occur so we can trace them better please?

View this thread on the Works forum...