|
-
Jul 31st, 2002, 03:19 AM
#1
Thread Starter
New Member
ADO vs DAO
I am developing an application with VB.Net. Currently I am storing my data in an Access 2000 database. Should I connect to this databse via ADO or DAO. I am more familiar with DAO because I have used it when developing applications in Access. I have been told that using ADO was pointless because I am using Access and not SQL Server.
However, I want to develop this application with scalibilty in mind. I may in the future choose to move over to SQL Server and I would like to develop my front end so that the transition would be a simple one. Keeping this is mind, Does anyone have some suggestions as to how to go about developing the front end? Should I create a code module that connects to my database? Or should I connect to the database with each form i create?
Thanks.
-Chris
Last edited by ChrisMalter; Jul 31st, 2002 at 03:23 AM.
-
Jul 31st, 2002, 08:22 AM
#2
Frenzied Member
I have been told that using ADO was pointless because I am using Access and not SQL Server.
Whoever told ou this is retarded, j/k. Seriously though, you should use ADO, and since you are using .NET, might as well use ADO.NET. This is much better than ADO imho.
Yes, use code modules for the DB, that way all your DB code is located at one centralized place. No hunting when ou want to change it latter.
-
Jul 31st, 2002, 08:38 AM
#3
neither. You use ADO .NET.
-
Jul 31st, 2002, 02:21 PM
#4
Hyperactive Member
Can u use the DAO Object in
.net
I thought it gone.
-
Jul 31st, 2002, 06:18 PM
#5
Thread Starter
New Member
Thanks
Thanks for the replies. I didn't realize there was a difference between ADO and ADO.NET. I haven't looked into it yet, but I guess now I should start. Anyone recommend where to find some good articles on ADO.NET?
-Chris
-
Aug 1st, 2002, 12:13 AM
#6
PowerPoster
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|