It seems to me that this would add unnecessary complications, without much benefits. I would like to know what advantages you perceive of such an approach.
>I’ve written an application of medium complexity which uniquely relies upon one table of simple structure (no Memo fields involved). The table (and the power of VFP) mimic all the tables and fields needed, with logical database normalization (master-detail), avoiding redundance as well. No Create/Alter Table will be necessary for adding new functionalities.
>After one year of upgrade and real usage, pros and cons are clearer.
>I want now to write and explain about the experimentation.
>To begin with, I’m looking for articles over the Internet pertaining the idea of reducing the number of relational tables tipically used by applications.
>A search through Google didn’t help.
>So I’m asking for useful links about the topic.
>Thanks.
>
>Bruno Maddalozzo
>MCP
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)
