>>>That would be a good idea if I would need to know general information about the field.
>>>I need an exact structure information. I need to make sure that I will not get numeric data overflow error when saving to the server. So if my structure allows 9999999.99 number, the field in the view/cursor coming from the SQL server will be 999999999.99. And If I will not limit entry by formatting the field, the user can potentially enter a higher number.
>>>
>>
>>What no business classes between the application and the data? :-)
>>Tim
>
>Good point. How you're suppose to structure biz object and how UI will interact with BO?

Business objects are classes that sit between the UI and the data access. The UI makes all it's request for data to the business object which retrieves the data and passes it back to the UI. The important one here is all the saves are requested via the business object also and the rules are checked (required fields, length of numbers "wink wink") before the business object attempts a save to the database.
Tim