vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| When we deploy applications, we have been using DSN's set up on the users systems. Then in the sqlconnection string, we go "dsn = xyz". I tried this with our new application, which is the first to be done with ADO.net and I get the following run time problem: "An exception 'System.ArgumentException' has occured in <Myapp>". I do the run time debugging and it tells me: "Keyword not supported: 'dsn'. For those who have migrated to .Net, how do you handle this issue? I mean, we are going to distribute this application, and our users will have different names for their servers, so how do we specify a data source dynamically. The way we have it for the moment is that we read the information from a config file. But it seems like there must be a better way. What happened to dsn? Any help on this would greatly appreciated. Thanks, Ed Hawkes |