Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / March 2005

Tip: Looking for answers? Try searching our database.

Missing OLEDB provider (second attempt)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jim Linder - 14 Mar 2005 17:37 GMT
After installing Visual Studio 6 with spk6 to a Win XP desktop, I cannot
create a data connection with an OLEDB provider.  The ODBC 'Select Data
Source' interface pops up instead of the OLDB 'Data Link Properties' dialog
box.  Both ODBC and OLEDB providers were selected in the Visual Studio 6
install.  I received the same results in Visual Studio 6 when installed on a
Windows 2003 server.  Other tools like Analysis Manager can find the OLEDB
providers in the Win 2003 server.

Signature

Jim Linder

Rhett Gong [MSFT] - 15 Mar 2005 11:12 GMT
Hi Jim,
Based on my understanding, you get ODBC 'Select Data Source' interface
instead of OLEDB "Data Link Properties".
I suggest you try reinstalling MDAC and let me know if you can resolve this
problem.
MDAC can be downloaded at:
http://www.microsoft.com/downloads/results.aspx?productID=&freetext=mdac&Dis
playLang=en

Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
Jim Linder - 15 Mar 2005 16:37 GMT
Re-loading MDAC 2.8 did not correct the problem.  Just a reminder, I
experience the same problem on two other PC's I tried this on.  A windows XP
professional PC and Windows 2003 standard server.

Is there an alternate way to add an OLEDB data connection in visual studio
6?  In the past selecting the option to add a data connection would
automatically launch the OLEDB 'Data Link Properties' dialog box.  Now it
launches the ODBC 'Select a Data Source' dialog box.  I also tried removing
the ODBC install option in the VS6 install onad only selecting OLEDB, but the
results are the same.

> Hi Jim,
> Based on my understanding, you get ODBC 'Select Data Source' interface
[quoted text clipped - 11 lines]
>
> This posting is provided "AS IS" with no warranties and confers no rights.
Rhett Gong [MSFT] - 16 Mar 2005 07:26 GMT
May I ask what language you are using (vb, vc6...)?  
And what you are really trying to get?
I think you are trying to get the connection string from oledb connection
wizard. If this is the case, you can simply create a .udl file in desktop,
double click it and finish all steps. Then drag the udl to notepad, you
will get the connections string as you requested.

Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
Jim Linder - 16 Mar 2005 16:35 GMT
I am trying to create a Data Project in VS6.  When I attempt to create an
OLEDB data connection to an ORACLE or SQL server database, The ODBC 'Select
Data
Source' interface pops up instead of the OLEDB 'Data Link Properties' dialog
box.

As you suggested I created a UDL file but when I select Add a DATA
Connection in the VS6 Project Explorer window, the ODBC Select a Data Source
dialog come up and it does not recognize the UDL file.

Dragging and dropping the UDL file to the VS6 Project Explorer window
accepts the file, but the Data View window selection does not get enabled, so
the tool is still useless.

Have you tried creating a data connection in VS6 on either a Win XP or Win
2003 PC?  I have tried it on 3 recent build PC's and have gotten the same
results.  This process does work on Win 2000 and older PC's.  

Also, I am able to create an OLEDB connection to the Oracle server using
Analysis Service on the Win 2003 PC, so I don't think there is a problem with
MDAC or Oracle SQL Net.  SQL2000 Query Analyzer can also create connections
to other SQL server databases from the Win 2003 PC and I think that uses
OLEDB also.

> May I ask what language you are using (vb, vc6...)?  
> And what you are really trying to get?
[quoted text clipped - 9 lines]
>
> This posting is provided "AS IS" with no warranties and confers no rights.
Rhett Gong [MSFT] - 17 Mar 2005 07:04 GMT
It sounds very strange. If the oledb dlg pops up in other applcation in
your system, then double clicking on a udl file should have the oledb "data
link properties" popup.  
For a simple test, I create a mfc application with VS6 on XP and 2003, I
checked the "database view with file support" and click "data source"
button, I get a "database option" dialog popup, selcect oledb and client
"select ole db datasource", i can successfully get the oledb  "data link
properties" popup.

I am not very sure what you see by dbclicking the udl file,  could you post
a screen capture here to let me see what it is please?  

Thanks and regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
Jim Linder - 17 Mar 2005 20:39 GMT
I can create a UDL file that has an OLEDB provider.  The problem is that the
VS6 'database project' does not provide a dialog that allows me to read it
in.  If I darag and drop the UDL file into the VS6 project, it accepts it,
but does not seem to recognise the UDL file as anything more than a text
file.  I was hoping it would enable the 'data view' after the file was loaded
to the project, but it does not.  So this does not provide a workaround to
the main problem below.

The steps I am doing are:
Start VS6.
Create a 'New Database Project'.
The ODBC dialog box 'Select Data Source' pops up.
Cancel out of that.
Try to add a data connection to the project.
The ODBC dialog box 'Select Data Source' pops up.

I cannot find in VS6 where to get it to create an OLEDB data connection when
run in Windows 2003 or XP.

Have you tried creating a 'database project' in VS6 when running on a
Windows 2003 or XP PC?

> It sounds very strange. If the oledb dlg pops up in other applcation in
> your system, then double clicking on a udl file should have the oledb "data
[quoted text clipped - 14 lines]
>
> This posting is provided "AS IS" with no warranties and confers no rights.
Rhett Gong [MSFT] - 18 Mar 2005 07:00 GMT
Thanks for your details steps.

VS6 Database Project only uses system ODBC data source, that is why you see
the ODBC dialog instead of OLDB  dialog. I've confirmed with our engineer
on Visual Studio,  by design "Database project" in vs6 only supports ODBC
datasource.  

Best regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
Jim Linder - 18 Mar 2005 16:41 GMT
The response from the engineer concerning a VS6 database project only being
able to add ODBC data connections is very suprising.  

I have used VS6 for quite a few years installed in Windows NT and Windows
2000 PC's.  I have always been able to add (and still can add) OLE DB data
connections to Oracle and SQL databases from within a VS6 database project
when using a Windows 2000 PC.  I was attempting to upgrade to Windows 2003
when I discovered this deficiency in how VS6 works on Windows 2003 and
Windows XP.

Would you ask your engineer why it is possible to add an OLE DB data
connection when VS6 was installed to NT or Windows 2000 but is not possible
when VS6 is installed to a Windows 2003 or Windows XP system?

> Thanks for your details steps.
>
[quoted text clipped - 9 lines]
>
> This posting is provided "AS IS" with no warranties and confers no rights.
Rhett Gong [MSFT] - 21 Mar 2005 06:53 GMT
Hi Jim,
I have installed the whole Visual Studio6 in a Windows2000 box and then I  
have the sp6 installed and created a new "Database Project",  what I only
get is the ODBC dialog.
Since there is no error in the installation log, so far as I can tell, this
should not be a problem in Visual Studio Setup. You could have it shown in
your Windows 2000 box, that may be because you've installed some 3rd party
plugins to enable it or something else.  
Since you would like to use "database project" to manipulate database
objects and data and you are a MSDN subscriber, I suggest you try vs2003
database project. It should give the same result both in 2000 and XP.


Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.