Mike Broderick
asked on
Visual Studio 2010 There is no editor available for ...
When I try to edit a form I get the error. Some background.
I recently uninstalled Office 2003 and installed Office 2013.
When I try to build the appl, there are 2 warnings regarding a reference to DAO:
Cannot find wrapper assembly for type library "DAO". Verify that (1) the COM component is registered correctly and (2) your target platform is the same as the bitness of the COM component. For example, if the COM component is 32-bit, your target platform must not be 64-bit.
The referenced component 'DAO' could not be found.
When I delete the DAO reference in visual studio, I can now edit forms, but when I run the application, I am unable to access any SQL database functions:
Provider: named pipes provider, error: 40 - Could not open a connection to SQL Server
I looked at the connection string; it is correct.
I recently uninstalled Office 2003 and installed Office 2013.
When I try to build the appl, there are 2 warnings regarding a reference to DAO:
Cannot find wrapper assembly for type library "DAO". Verify that (1) the COM component is registered correctly and (2) your target platform is the same as the bitness of the COM component. For example, if the COM component is 32-bit, your target platform must not be 64-bit.
The referenced component 'DAO' could not be found.
When I delete the DAO reference in visual studio, I can now edit forms, but when I run the application, I am unable to access any SQL database functions:
Provider: named pipes provider, error: 40 - Could not open a connection to SQL Server
I looked at the connection string; it is correct.
ASKER
I am OK with removing the 2003 stuff but don't know where it is in this project. When I delete the DAO object, I don't get any compiler errors. The runtime problem I do get seems to be in SQL objects. For example a Fill method on a SQL Adapter generates the message.
Again: before deleting DAO reference - cannot edit form. After deleteing DAO reference - SQL connect errors.
Again: before deleting DAO reference - cannot edit form. After deleteing DAO reference - SQL connect errors.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is in the form.load of the 1st form:
Dim con1 As New SqlClient.SqlConnection
con1.ConnectionString = "Initial Catalog=SVR1;Data Source=PROD;integrated security=SSPI;persist security info=False; workstation id=WS03;"
Try
con1.Open()
Catch ex As Exception
MessageBox.Show(ex.Message )
End Try
The message box shows after about 30 seconds.
Dim con1 As New SqlClient.SqlConnection
con1.ConnectionString = "Initial Catalog=SVR1;Data Source=PROD;integrated security=SSPI;persist security info=False; workstation id=WS03;"
Try
con1.Open()
Catch ex As Exception
MessageBox.Show(ex.Message
End Try
The message box shows after about 30 seconds.
ASKER
ex.Message contains:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When I delete the project an rename the backup back to the original, it connects to the server fine. Then when I (after making another backup project) delete the reference named DAO, it fails.
ASKER
The connection error was something I did. Sorry.
Office 2013 probably has also DAO included but by using a .NET component rather than by COM. you may consider to port your dao interface to the newer Standard. there should be a lot of sample code available for this task.
If you would install Office 2003 again, the issue also should be resolved. I don't think that there are any imponderables by doing so.
alternatively, you could try to get the redistributable package for either Office 2003 (it may be part of the office 2003 setup) of for visual studio 2003. search at MSDN for these packages which should include the needed dao common controls.
Sara