>Hilmar,
>
>>I also found (VFP 3) that the RI sometimes fails, and selects the wrong table. I had one table called "Article", another called "ArticleSupplier" (or something similar - it was quite a while ago). Note that "Article" $ "ArticleSupplier". In this case, RI might already have opened "ArticleSupplier", and decide to check there, instead of opening "Article"!
>
>That's a good one! However, if I look at the VFP RI code, the mixup would occur between "ArticleSupplier" and "Supplier". This has to do with the manner of how it remembers which tables are opened by the RI builder. I checked my RI code, and saw that here the same problem might exist. I'll take inmediate action to solve the problem.
Perhaps you already know the following trick: for instance, to make sure a table is already opened, you can use an expression such as:
";" + MyTable + ";" $ ListOfOpenedTables, where ListOfOpenedTables might contain ";Article;Supplier;ArticleSupplier;"
>If I look at the VFP RI code, the same problem is still in it today.
>Thanks again,
Damn! So I am correct in taking preventive action ("ArticleMain" rather than "Article").
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
