Hi Cetin

>If I understood correctly, u* tables are support tables ... audit tables?

Yes, this is true and given time they can be recreated programatically from the existing data.

>I think it would be better to create them as views or no views at all, just specialized routines to build them as cursors anytime.

I had though about this as a view, but what stopped me is that the SQL statement will be getting larger and larger (lots of unions? or is there a better way to combine from various tables?) as I keep adding Parent-Child table sets, of course there will be an upper limit to the no. of sets that will be in the final app. but as of right now I will be starting with the basic sets.

>Downside of this approach is that either a view or a cursor needs time to build whereas a support table is ready out of the box.

The out of the box was what had attracted me to this idea in the first place, of course it took it's toll on me, plus when I had started out I had zilch knowledge of SQL.

>However since reporting/printing etc are generally done with some filters that needed time might be as short as a blink of eye. Pros of this approach is that you avoid the redundancy of data.

I like this idea of avoiding redundant data. One more compelling reason I had fallen for Audit Table was that the user had requested automatic generation of narrations for printing in the ledger, for eg. for the sale account entry in uJournal.Narrations fields I would have generated and stored such a narration "Invoice no. 1, M/s. ABC Ltd., Rs.12345.67" for the party account entry in uJournal.Narrations I would have generated "Invoice no. 1" and so on for each and every account affected. This I do not see can be done in views nor SQL Pass-Thru?

In fact, I have a Narrations Master with one record for each type of entry that will possibly be generated so the above 2 narrations will be stored in this master as follows: "'Invoice no. ' + ALLTRIM(STR(tSale.billno)) + ', M/s. ' + ALLTRIM(mAccounts.Name) ..." and "'Invoice no. ' + ALLTRIM(STR(tSale.billno))" I eval this at the time the audit table entry is generated and store it in the narrations field. Any way to duplicate such in either views or even SQL Pass Through?

>SQL server can partition a table based on some criteria (ie: based on year, it creates a single physical table for each year,

Wow this is a nice feature. For multiple year's currently I make the user start a new company which has the tables physically seperated in seperate folders.

>depicted here as I see that one of the best features of SQL server:).

Agreed *g*

>Lots of other new features that make u* unnecessary (if I understood their purpose right -

No you were right in understanding me.

Thanks for responding to such a broad area post of mine.