VB 2008 / SQL Server 2008 - Recordset Retrieval via Stored Proc.
I'm pretty new with Visual Studio 2008 but have done VB6 development for the past 8 years straight.
I'm trying to figure out how to rewrite a couple of personal VB6 apps. at home just for fun and for a learning experience w/VB 2008.
I typically don't retrieve any data into my VB apps. w/just straight SQL queries... I always utilize stored procedures in SQL and call those via the VB apps... much cleaner VB coding that way in my opinion.
(I'm talking about Windows Forms development here... just an FYI...)
I can't for the life of me figure out the exact syntax that I'll need to use in Visual Basic 2008 in order to (for example) retrieve a list of values, let's say, into a combobox. I can do that in my sleep in VB6, but I'm just behind the learning curve w/the syntax in .NET to do that.
Anyone have any specific code snippets/examples that they could post for me in knowing the appropriate syntax to use in retrieving records into a recordset in VB.NET via a SQL Server stored procedure?
Is there a reason why you want to use ADO with VS2008 instead of ADO.Net?
Please post questions to the forums, where others may benefit.
I do not offer free assistance by e-mail. Thank you!
I'm perfectly fine using ADO.Net... as I mentioned before, I'm way behind the learning curve in having been doing VB6 development for so long, so I'm likely unaware of several new/preferred technologies with VB 2003/2005/2008.
Originally Posted by kmoorman
I typically use unbound recordsets (aka disconnected recordsets) in VB6... do you have the choice of bound/unbound recordsets in VB.net 2008 or are they all unbound, all bound, etc?
Recordsets as such don't exist in ADO.Net.
ADO.Net is a completely disconnected data architecture. There is no direct support for server-side cursors, etc.
You might want to start by looking into ADO.Net's connection, command and datareader classes.
Another area to invesigate is ADO.Net's dataadapter, dataset and datatable classes.
Also keep in mind that the various data access classes are grouped together based on the particular database being accessed. So, for example, SQL Server uses the SQLClient namespace with its SQLConnection, SQLCommand and SQLDataReader classes. MS Access uses the OleDb namespace with its OleDbConnection, OleDbCommand and OleDbDataReader classes. Etc.
Many thanks for all of the helpful postings... I'll check into the various items/links a few of you posted... thanks again...
Hopefully you will find this helpful with respect to ADO.NET
I don't answer coding questions via PM or Email. Please post a thread in the appropriate forum section.
Please use [Code]your code goes in here[/Code] tags when posting code.
Before posting your question, did you look here
Got a question on Linux? Visit our Linux sister site.
Modifications Required For VB6 Apps To Work On Vista
By GHETTO.CHiLD in forum .NET
Last Post: 04-20-2007, 09:59 AM
By Michael in forum Database
Last Post: 03-17-2005, 12:07 PM
By Pete in forum Database
Last Post: 02-14-2002, 02:58 PM
By Kermit Goodman in forum VB Classic
Last Post: 12-21-2000, 08:14 PM
By Becky in forum Database
Last Post: 07-11-2000, 04:27 PM
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL