Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Visual Basic > VB 6 Visual Basic 6 > Pro VB Databases
|
Pro VB Databases Advanced-level VB coding questions specific to using VB with databases. Beginning-level questions or issues not specific to database use will be redirected to other forums.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Pro VB Databases section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 21st, 2003, 11:30 AM
Registered User
 
Join Date: Jul 2003
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default Requires an OLE DB Session Object


Hi,

Running VB 6 Components on a server connecting to a SQL Server database. Recently we started receiving this error.

"Requires an OLE DB Session Object, which is not supported by the current provider."

This has been working for over 8 months now and all of a sudden we started receiving this error. Could this be an ADO error?

Thanks
Robert


 
Old July 21st, 2003, 11:34 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 128
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Don't have any answers yet, just a few question though.

Have you made any changes to your application involving calls to your database?

When does this error occur? When it is trying to connect or when you make some type of request?

Larry Asher
 
Old July 21st, 2003, 11:41 AM
Registered User
 
Join Date: Jul 2003
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default


No changes to DB stuff. Updated references - we did move up a version in MDAC.

It happens on our first Stored Procedure call.

 
Old July 21st, 2003, 11:49 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 128
Thanks: 0
Thanked 0 Times in 0 Posts
Default

My thought would be either the server\client or the application is not up to date with your latest rev of the MDAC.

Initially, I would think if you installed the MDAC upgrade on the client, where your app is running, and you did not recompile your application. No harm would be done because the upgrade should backwards compatable.

But, if you installed the upgrade on your development computer and recompiled the application without upgrading MDAC on the client machine or the DB server you could have some problems. I would expect you to have problems in this case.

I would look at making sure MDAC is current on all of the machines and that your application is compiled with the current MDAC rev also.

Hope this helps.

Larry Asher





Similar Threads
Thread Thread Starter Forum Replies Last Post
OLE-DB grstad Classic ASP Basics 7 January 28th, 2007 09:25 AM
If any one knows How to develop ole db anjicafe Visual C++ 0 June 15th, 2005 09:01 PM
Err with OLE Db Connection DARSIN General .NET 2 June 9th, 2005 11:21 PM
OLE DB Driver knowledge76 Access VBA 2 April 21st, 2005 11:34 AM
Connecting to Access via OLE-DB mairejo Access 3 October 26th, 2004 02:28 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.