>You make my mouth water... OK, I'll put it on my to-do list immediately, so I don't forget it. Any limitations in the TaxRiBuilder? I think I remember somebody mentioned that it doesn't accept composite keys. That wouldn't be a problem for me; as you know, I use surrogate keys.
Walter,
I also want to add that I had the opinion, a long while ago, that VFP generates inneficient code. Hardcode every table into the individual RI-functions, oh my! And lots of repetitive code.
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"!
It required some hours of tricky debugging to pinpoint the problem. I decided to avoid such situations in table names (currently, in another system, I have an "Article" table too - but it is now named "ArticleMain", to bypass the problem). I didn't investigate whether the problem was solved in later versions of VFP.
Hilmar.
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)
