Everything was working well yesterday, but today when attempting to open and preview one of the queries of a tableadapter in my application's most crucial dataset, generates this error:
"Operation failed."
"Unable to find connection 'MyConn (MySettings)1' for object 'MySettings'. The connection string could not be found in application settings, or the data provider associated with the connection string could not be loaded. .'
I've searched these forums, newsgroups, google and come across a few examples of where the dataset designer has inserted additional connection lines within the xsd. However, this doesn't appear to have happened here.
If I get the latest stable build in its entirety from SourceSafe, I still have the same problem!
If I get a very old build from SourceSafe, I still have the problem!
This proves that there is nothing wrong with the xsd. Or, each time it is used, the Dataset designer goes off and does its own thing with it.
I'm able to open and configure the Query and using the Query Builder, execute a test of the query - which does exactly what I would have expected from the "Preview Data" button.
If I run the solution, no immediate problems. But calling the update method on one of the affected tables (although I get the error on ALL my datasets) at runtime (the solution compiles ok and runs) I get various SQL errors related to concurrency. One of my datasets bombs out when I attempt to open it with the above error, and additionally displays a critical message: "The specified procedure could not be found. (Exception from HRESULT: 0x8007007F).
The solution is a VB.NET solution, and this is a data access layer .dll assembly. The connection string is stored in MySettings.
Incidentally, I have tried to log a support incident with Microsoft, but can't as the online tool doesn't recognise my product ID when I type it in or use the downloadable tool. Does this indicate a potential problem with my VS2005 installation?
Please help, I'm absolutely tearing my hair out! (And so is my client - the solution was opened to issue a hotfix!)
Also my VS2005 installation, after 5-6 hours continuous work uses up around 1.5gb of RAM. Connected problems?
Many thanks!
(p.s. BRING ON VS2005 SP1!!!)