Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
stoland
Starting Member
5 Posts |
 Posted - 2007-07-03 : 09:34:47
|
I have an ASP.NET/ADO.NET page i wrote. It was based off of the development database during most development, and it switched over seamlessly to the production database.Except for yesterday, when i went back to edit the page. It simply stopped returning results on my queries. To see if it was caused by bad values being passed to the sqldatasource, i tried it in the "Configure Data Source..." window, and it returns zero rows. When passing all of the exact same parameters to the same procedure in the same DB engine, even using the same login information, it works.Just not in my ADO.NET app anymore...Can anyone tell me what the hell could be going on here, please? I already rebuilt the page from an older version this morning, being very minimal on changes, and the last thing i changed before it stopped working was the connection string... *BUT* I have triple-checked that against the canon string we have always used in every working copy.I'm losing a lot of hair over this  . Any help would be greatly appreciated.Thanks in advancestoland |
|
|
stoland
Starting Member
5 Posts |
Posted - 2007-07-03 : 11:57:23
|
| OK, so the plot thickens. I have now redone this page 3 times from an old copy, and as soon as any of the SQLDataSource objects are modified (or the configure wizard gone through) they stop working. Does this sound at all familiar to anyone?Much ThanksstolandPS: (To Mods) Sorry about the cross-posting, realized there were much more relevant forums for me to post this thread on |
 |
|
|
stoland
Starting Member
5 Posts |
Posted - 2007-07-03 : 13:32:55
|
 My badI figured out what it was - while i could choose to not provide values (in direct SQL mode) for arguments that had default values, i could not from ADO.NET.Anyway, thanks for looking and.. stuff  I'm sure ill be back more in the future, my job now having to do largely with MS-SQL, and my main database experience being with MySQL and SQLite on *NIX.Thanksstoland |
|
|
|
|
|
|
|
|
...Works in Management Studio, Not in .NET anymore