Permissions???

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi, all:

Dev Tool: VB6
Server: SQL Server 2000.
Environment: Windows 2000/Windows XP/Windows 2000 Server

I had an ADO conection to the from a VB Application, wtih this connection
the user could Write/Read data from server and execute stored procedures.

The connection was made with DSNs(ODBC). The system created the DSNs and
connected to the server. Now, since we discovered that any one ,who had
Office 2000 or XP, could connect to the server and have the same permissions
of the VB appliacation user (through the DSN the sytem created), we decided
to do this:
1. Use a DSN-less connection
2. Validade the user with SQL Server authetication(not by the tursted
connection.
3. Give theses users the same permissions they had before.

Now, the system has a huge number of calls, updates and stored procedures,
my problem is that the system now nevertheless can use simple SQL-transact
staments with no prblem; ADO gives the following message when using stored
procedures:

"Operation is not Allowed when the Object is closed."


If the permissions were the problem, I couldn't execute the procedures
in the Query Analyzer using the same connection, UserID and Password I
developed for the VB6 application user.

So, I suspect the problem is not the connection itself, there is something
in my ADO (v 2.5) statement(¿?).

Here is the stament:

strDSN_p= "Provider=SQLOLEDB;Persist Security Info=False;Initial
Catalog=MyDB;Data Source=MyServer;User Id=SomeUser;Password=somepassword;"

cnADO_p.ConnectionString = strDSN_p
cnADO_p.CursorLocation = adUseClient
cnADO_p.CommandTimeout = 400
cnADO_p.ConnectionTimeout = 240
cnADO_p.Open

where cnADO is an ADO connection object.

Any ideas??? I'm really worried because most of users have Office in their
computers and some them are system engineers in manegement possitions(not in
the computer department!) and data must be protected(DSN connections are
trustless!).



Note: A public permission has been granted to All the stored procedures.




--
Rick

.

Relevant Pages

  • Re: Cross Transactions between ADO & ADO.Net
    ... connection--it thrashes the server unnecessarily and discards useful server ... goes away and quietly reopen the connection when they return. ... > DTC transactions are not only heavy, they might also cause deadlocks due ... We even call ADO ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Permissions???
    ... > Server: SQL Server 2000. ... > the user could Write/Read data from server and execute stored procedures. ... > The connection was made with DSNs. ... ADO gives the following message when using stored ...
    (microsoft.public.data.ado)
  • Re: Help!!!
    ... Ensure your stored procedures include 'SET NOCOUNT ON'. ... > Server: SQL Server 2000. ... > I had an ADO conection to the from a VB Application, ... > The connection was made with DSNs. ...
    (microsoft.public.sqlserver.security)
  • Re: Outgoing POP3 email missing/lost/not received
    ... Funny thing is that I have had this ISP for 8 years and it has always been ... It looks like when you last ran CEICW, you set the ISP's mail server to: ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect client to server 2003
    ... you need to reconfigure the IP schema of your SBS ... On the SBS 2003 Server open the Server Management console. ... On the Connection Type page, click Broadband, and then click Next. ... Alternate DNS server, type the IP addresses that are provided by your ISP ...
    (microsoft.public.windows.server.sbs)