>>Hi
>>
>>I have a collection of data-objects in my app, I want to use these data-objects to hold certain values to keep things in the app up to date. Is this a good idea?
>>
>>For example, I have a USER data-object, that can add/edit/delete records, but also contains functions that can be called by it's parent, and may also validate usernames/passwords and also hold the currently logged in userid, userlevel etc.etc.
>
>Generally speaking, it sounds to me like you are describing an ordinary business object. (It would talk to a data object that does the actual data-related stuff like add, delete, save records, say).
>
>So, yeah. In my mind a user business object would have this functionality.

So, if I was writing a 3-tier app, my business object would obviously reside in the middle-tier, but does that mean that the data-object does too? Or is that part of the data-layer?

Thanks
Kev