-
Hi,
I'm writing a large app with VB and SQL server and was intersted on some thoughts about the best method for data access:
1. Should I stay away from data controls and stick to code?
2. Is it better to use data class DLLs. If so, if there a way to share 1 connection value among various pieces of the app?
Lastly, and my biggest question is, right now the app is one large monolithic exe that I want to break up into modules. What is the best method to break up forms in an app into different modules yet share information between them?
-
ADO gets my vote too!
-
Sorry to disagree, but any professional type of database app should not use data controls.
I can't beleive any complex systems would use data controls.
Yeah sure use ADO but not a data control. Learn to code without them, you'll be a lot better off in the long run.
You do not need a data control to connect to a database, SQL Server or otherwise.
-
TRUE!
Okay...I must confer with Stevie. He has proven me wrong regarding data controls. But I must say that ADO is what you need.
Good Luck and let us know how you're doing.
-
Hi, let me join u all with my views.
I think the best way for database communication would be through code. I always prefer this because i can have more control over the Data being used and updated.
I would suggest you to use Dlls wherever possible, as they are supposed to help you provide a way of organising your code.(Atleast nearly that) and as for the sharing of connection part, well, i am not really sure of it and i dont want to confuse you with my half-knowledge.
As for ur last question, this was what i have learnt thru my little experience. Use a concept called layers. Heard a lot of them out there saying User Layer, Business Logic Layer and the Data Layer(They also call this the three-tier architecture???). The User Layer would consist of the User Interface and the client side Data validations, the Business Logic Layer or the Business Layer(whatever it is) and the Data Layer could be present on the Server Side. The Business part contains all ur business logic implementations and the Data Layer deals with the communication with the Database. So, that was how we could use the Business Layer but writing them as DLLs and placing them on the Server Side.
Well, i am sorry if it only increased ur confusion.
This information stands to be corrected. Please do so if i am wrong.
All the best...vijay.
