> That is generally more robust, since your design makes referential
> integrity more complex. A treeview is not a database structure, it
> is a user interface. A database *stores* data. It does not (and
> should not) dictate to the user interface; and the user interface
> equally should not dictate the database structure.
>
> The "Q" in "SQL" means "query". The whole concept of a query
> language is that you can generate output, via SQL, in any structure
> that your user interface demands, including flattened structures such
> as you have set up to "fit the shape" of your treeview UI.
wow..woo.. just a simple chat and you almost can see all my
implementation. My Treeview implementation that cover almost 80% of
the application do really dictate my database structure. I will be
back with actual modified table structure and any SQL involved
later..so this will not bear to OOT.
> >
> >yes, the currency field may have very high number (billion, FYI my
> >currency is Indonesian Rupiah) for single record entry and could be
> >more than billion for Total field. I just need 2 digit after decimal
> >and it will highly used. What is proper data type for handling my
> >currency?
> >
mmm... what about above question, any suggestion? will NUMERIC(18,2)
be sufficient enough?