dataset, datagrid, please help.

nurbi

New member
Joined
Feb 17, 2014
Messages
2
Programming Experience
3-5
I'm using Visual Studio and Oracle DB.

First of all, sorry for my english..

I want to make a program to enter registers to a DB, these registers can be modified, deleted, etc.. Also you can make querys show all fields, etc.. in a datagrid.

I have done it with sql querys, datareaders, datasets, adapters, etc... but I'm thinking about change the program to improve it and make it easy to be modified. My doubt is, if I want to create classes to do a good application I have to do the querys, create objects, save it in arrays, put it in datagrid. I think this way is too expensive about the memory and time.

How can do it better? What is the best way to do that?

Thanks!
 

jmcilhinney

C# Forum Moderator
Staff member
Joined
Apr 23, 2011
Messages
3,140
Location
Sydney, Australia
Programming Experience
10+
It's not going to be too expensive with regards to memory if you write properly and it will take more time to create in the first place but the point of taking that time now is that it will save you time in the future when maintaining the app. For one thing, if you isolate the data access code from the UI then you can later work on fixing or extending the data access code without having to worry about inadvertently breaking the UI and vice versa. You should read a bit on n-tier architecture, which is about separating the logic of the application into tiers that each depend only on the interface of the others and not on the implementation.
 

nurbi

New member
Joined
Feb 17, 2014
Messages
2
Programming Experience
3-5
Thanks

It's not going to be too expensive with regards to memory if you write properly and it will take more time to create in the first place but the point of taking that time now is that it will save you time in the future when maintaining the app. For one thing, if you isolate the data access code from the UI then you can later work on fixing or extending the data access code without having to worry about inadvertently breaking the UI and vice versa. You should read a bit on n-tier architecture, which is about separating the logic of the application into tiers that each depend only on the interface of the others and not on the implementation.
Thanks!

Now I'm looking for a ORM to work, I think that way will be the best.
 
Top Bottom