Posts Tagged ‘dataset’
I recently had the need to implement transaction tracking between two separate databases on two separate servers.
Unfortunately, I could not be sure that DTC was implemented on either server, so using transaction tracking with the TransactionScope wasn’t an option.
I also wanted to be able to wire this in easily to the existing 3-tiered framework we are currently using so that what I ended up with could easily be implemented by other developers in a similar situation.
Last week I demonstrated how to access data from a web service in Silverlight and display it on the page. Today we are going to continue on with that demo and look at how to navigate through our data.
As I’ve stated in previous posts, Silverlight doesn’t work quite the same way as we are used to in ASP.NET or in Windows Forms. But if you’ve been following along, you’ve seen that much for yourself.
I’ve seen this error a couple of different times. Mostly from other people calling me with the problem. So I still don’t know what ultimately causes the problem. But if you’re having this problem, here’s how you fix it.
First, a bit of background.
You’ll open a dataset you’ve been working with for months and see the following error message:
Unable to find connection [connectionName] (web.config)1 for object ‘Web.config’. The connection string could not be found in application settings, or the data provider associated with the connection string could not be loaded.
There are cases where it is advantageous to have a separate sql login for each user login who will be editing your database. If you are using Windows authentication, this is not a problem because you can pass the windows authentication tokens on through to the db without having to do a whole lot of work.
But, what about times where setting up a separate windows user for each person who will be accessing the system is more work than it’s worth, or as is the case in shared hosting plans, just isn’t practical?
Last Thursday, we looked at how to replace the TableAdapter with our own TableAdapter as a way or eliminating our dependence on Microsoft SQL. The problem with this implementation is that every time you want to switch databases, you’ll need to switch what TableAdapter the code is using.