construction — Fri, 14 Jul 2006 09:22:52 +0000

Hey thanks JeevesBond.

SBalan Group
http://www.sbalanprojects.com/

JeevesBond — Thu, 13 Jul 2006 12:32:32 +0000

Well, I don't use .NET (and when I do it'll probably be under Linux ), so it'll have to be VB6! Here're the steps I used to hook up an ADO control to one of our SQL Servers:

Started new standard exe VB project.
Added an ADO Control to the form provided (this is msadodc.ocx you're asking about isn't it?).
In the properties box for the ADO control I navigated to the "Connection String" property, and started the wizard by clicking on the ...
From the dialog I then opted to "Use Connection String" and clicked the "Build..." button.
From the next dialog I selected "Microsoft OLE DB Provider for SQL Server" then clicked "Next"
I then filled out the server name, selected Integrated NT Security, selected the Database and then clicked "Test Connection". If this fails you need to scrutinise your settings thoroughly.
After all that I ended up with a connection string that looks like this:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=ExecUKTest;Data Source=EXECDEV'
I pressed ok and now have the connection to my server.
Then selected the "RecordSource" property's "..." to bring up another dialog.
In that dialog selected a Command Type of "4 - adCmdStoredProc".
Then selected the "Table or Stored Procedure Name" drop-down box, which gave me a list of the Stored Procedures available on the SQL Server.

That should do it for you. Hope that helps.

construction — Wed, 12 Jul 2006 09:31:06 +0000

Hi JeevesBond...
Yes, it is Stored Procedures. Its ok if u can let me know how the same can be done using VB6.

Thanks:)
SBalan Group
http://www.sbalanprojects.com/

JeevesBond — Tue, 11 Jul 2006 12:01:02 +0000

By backend procedures do you mean Stored Procedures on some SQL Server? Secondly are you using VB6 or VB.NET, I can check in VB6 but would have to go a little further to find out for .NET