Hi!

My understanding is the same (between the UI and DataAcces-DataStorage) the reason why SQL2005 would/could call it is that all that logic is in one place (in the BO)

Sarosh

>Why SQL2005 would call them. However if you need in any case SQL2005 is much more programmable than SQL2000. It's not a trivial topic IMHO (there are samples in SQL2000 books online, SQL2005 further has programmatibility with C#).
>BO is a fuzzy term for me. I'm not always clear what layer someone is referring to when saying BO. My understanding is that it's between UI and DataAcces-DataStorage.
>Cetin
>
>>Hi!
>>
>>Ok, that make sense.
>>
>>Can SQL2005 call my BO's?
>>
>>Sarosh
>>
>>>I didn't say use BO but it's perfectly valid depending on your needs. However if BO is in the play it's arguable that any direct data access should occur. If you use BO you could provide services (COM,XML web service -maybe even .Net objects via remoting-) and your users ask to BO for data, not directly to DB.
>>>Cetin
>>>
>>>>Hi!
>>>>
>>>>Yes of course but my question was if we use BO's to do the calc's then how will users create user defined reports on the fly.
>>>>
>>>>e.g. Use MS Access and connect to the DB and create their own reports based on the tables and or Views etc.
>>>>
>>>>Sarosh
>>>>
>>>>>I'm not sure I understand. Either directly in SQL server or in BO you're doing it independant from UI.
>>>>>Cetin
>>>>>
>>>>>>Hi!
>>>>>>
>>>>>>Thank you both for your suggestions.
>>>>>>
>>>>>>Now would this change if we were to later at some point move to the Web (UI)
>>>>>>
>>>>>>Sarosh
>>>>>>
>>>>>>>>Hi!
>>>>>>>>
>>>>>>>>We are in the process of creating a new Application which has quite a few calculated columns. The App will be Windows based and will use SQL 2005 as the database.
>>>>>>>>
>>>>>>>>The application's UI will be like a spreadsheet (Grid based) and will also have lots of Reports (pre built and user defined) which need to use those calc columns.
>>>>>>>>
>>>>>>>>SQL 2005 has the ability to create calculated columns so my question is how should we go about this.
>>>>>>>>
>>>>>>>>1] Define all the calc cols in the DB and have the BO's, UI and Reports treat them like regular cols.
>>>>>>>>
>>>>>>>>2] No calc cols in the DB and all the calc done by the BO's if so then what happens to (user defined) reports etc.
>>>>>>>>
>>>>>>>>3] Some other combination.
>>>>>>>>
>>>>>>>>Thanks
>>>>>>>>
>>>>>>>>Sarosh
>>>>>>>
>>>>>>>Sarosh,
>>>>>>>IMHO all are valid with 1st has advantage in reports. Other options like SQL2005's user defined types,CTE functions,pivot/unpivot,apply,StoredProcs etc exist. Really depends on your specific needs. Check user defined types anyway. They're powerfull in SQL2005 (codable in C# to have methods. ie: myType.convertToMetrics(),myType.ToString() etc so they even have advantage to format on the fly).
>>>>>>>Cetin