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 |
|
SimonGough
Starting Member
23 Posts |
 Posted - 2002-04-25 : 11:44:07
|
| We have just developed a system in VB and SQL Server 7. The Database was moved to it's new home and has been setup with the right users etc...The VB code is causing a bit of bother tho. not sure if it's a permissions thing on the db side.I connect to the SQL DataBase using SQL Server Authentication through a DSN.this works ok. The username typed in is then passed to a SP where it checks to see if it exists in the Users DB Table (used for verification purposes). This is where things go wrong. I don't think the SP is even executing as I get a Null Recordset returned which results in an error and program quit. The same code & DB setup works fine on the development computer but not in it's new location.The one thing we noticed was that the new SQL Server properties stated that only Windows NT logins are accepted. We have changed that now though but still get this error.I hope I have explained myself well enough.Can anyone shed some light on this???Thanks for any help.Simon. |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-04-25 : 12:39:44
|
| We have a very similar setup for one of our databases. What is the error message exactly. Have you checked the syslogins table to see what logins exist ? What does your table structure and stored procedure look like ?Paul |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2002-04-25 : 13:07:51
|
| Check what permissions the VB code is using to execute the SP....no permission to execute -> no results, regardless of what the procedure does.One way to do this is to invent a usercode for the VB app, grant it permissions to execute the SP's and then work from there....HTH |
|
|
|
SimonGough
Starting Member
23 Posts |
Posted - 2002-04-26 : 07:32:14
|
Ok, I will check the syslogins table but I think the user is there.the error msg is just one I have told the App to return if no Recordset is found.As for permissions, I am connecting to the DB with the username and password for the SQLServer Login. The connection string looks something like this."dsn=" & strDSN & ";UID=" & strUsername & ";PWD=" & strPassword It connects ok.The user is assigned to a Role. In this case we have given the role access to the tempdb, pubs, master, MySQL-DB(The one we are working with) and also given the role execute permissions on all SP's and Sel, Ins, Update on all the relevant tables...Default DB for the user is the one we are working with.I know this is a bit over the top but we were just trying to see what was wrong...Anyway, should the master/temp/pubs DB's be set up in any special way??? I am sure this isn't a code problem as it all works fine on our office network. |
|
|
|
|
|
|
Permissions????