Advise on this architecture...

[rjlohan]

I'm making an exam db. I want a .dll/.exe component to do all DB work, and expose properties such as QuestionText, AnswerText, etc.

Is this an appropriate design:

clsDBAccess
-->LoadNewQuestion
-->GetQuestionText
 
clsQuestion
-->Propert QuestionText

The clsDBAccess does all the actual DB work, and is the only way to access this .dll's properties and methods. But, to break it up a little internally, I was gonna make separate internal classes to hold the properties for the Question, perhaps another for the Answers, I'll see how I go.

The question is - should I bother breaking it up internally? It would add an extra layer of function calls to retrieve properties, but I thought it may help in the design if it was broken up like this.
Although, it's not that complicated anyway, and probably wouldn't matter toooo much if I just had one class to do what I need.


Thoughts?

-RJ