By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,890 Members | 1,239 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,890 IT Pros & Developers. It's quick & easy.

Databases and object programming

P: n/a
I am creating an interface that is to be used for editing product information for our location. Currently I have written the main [Product] class and its routines and functions. I am starting to work on the sub objects of [Products] for instance Boxes.

Each product is packed in a box of a specific type. While I really had no trouble with the product class and its setup, I am thinking I could do things better, or differently. A box has 3 attributes, the Boxtype, BoxTare, BoxDescription. You would think that it would be easy to setup a class for this, but for somereason I am having design issues. Part of the reason is I am getting caught up in interface design and not the object design.

How do those of you who code data-bound objects do so? I think I am doing the tier development right. The interface edits the object, the object edits the database. But for instance, for the box editor I have 3 text boxes that display the information on the current box. I have a listbox that reads a datatable of the boxes table. I dont think I am doing this right. I should really have an object that is a collection of boxes that the listbox uses, correct?

I think I will leave it at that and answer specific questions as they are asked for clarification.

--Eric Cathell, MCSA
Nov 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.