Object oriented programming. Create instance of form

Dave

Hi,

I just need some advice on the best way to approach a project.

I need to create a form where users can enter data and this then gets written away to a database.

I will have a parent MDI form that lets you create child instances of the form so you can view/enter more than 1 at a time.

Do i create a form that holds or the methods i need for writing the data away and then create instances if this, or should i first be looking at writing a class that then creates an instance of a form. This class would then hold all the methods etc.

Im really just trying to see how anyone else would aproach this and to try and keep it inline with OOP.

Thanks

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Sam Hobbs14y ago
Are the forms for records in a table in the database? Is there a one-for-one correspondence of form to records? In other words, will each form be for one record of a table and will each record have at most one form for it?

How will the forms be opened? Will each form be used to add, update or delete a record? How will a record be selected for update or deletion?
Dave14y ago
Thanks for the reply. As there could be many instances of my form being created and updated at the same time within the MDI form, i think its probably best like you said to write all the code behind the form. Then create a instance from the MDI parent every time in need to create a new one.

Dave
Vulpes14y ago
Because of the way that Visual Studio works, I wouldn't write a class which creates a form.

If the database code is not too extensive and only needs to be called from one form, then I'd include the methods to do that within the form itself.

Otherwise, I'd hive off the database code into a separate static class - assuming you don't need multiple instances, there's not much point in creating a normal class. You can then call the static methods of this class from any of your forms.