Connecting from VB without knowing login/passwd?

Hello
One of our customers who uses a MS SQL-based application asked
us if we could write an add-on. We've never used MS SQL before. From
what I've read, it seems like ADO requires a login/password to connect
to it.
Problem is, the customer doesn't have this piece of information, and
although customers own the data, we don't want to ask the company that
built the main application because our add-on does something similar
to what they do (but better :-)).
Is there a way to either bypass the login/password phase, or sniff it
from the network? We just want to read data, not write anything to MS
SQL.
Thank you.> Is there a way to either bypass the login/password phase, or sniff it
> from the network?
that would pretty much defeat security in the first place...
Have your DBA create a login using appropriate permission in the database and specify that login. Of
course, that login could either be a SQL login (where you specify the login name when you connect)
or a login based on the Windows user (where you specify to use integrated authentication).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Gilles Ganault" <nospam@.nospam.com> wrote in message
news:1e1t831pk775sk5hlcha1uoaha07jfhb4l@.4ax.com...
> Hello
> One of our customers who uses a MS SQL-based application asked
> us if we could write an add-on. We've never used MS SQL before. From
> what I've read, it seems like ADO requires a login/password to connect
> to it.
> Problem is, the customer doesn't have this piece of information, and
> although customers own the data, we don't want to ask the company that
> built the main application because our add-on does something similar
> to what they do (but better :-)).
> Is there a way to either bypass the login/password phase, or sniff it
> from the network? We just want to read data, not write anything to MS
> SQL.
> Thank you.|||On Jul 6, 2:14 pm, Gilles Ganault <nos...@.nospam.com> wrote:
> Hello
> One of our customers who uses a MS SQL-based application asked
> us if we could write an add-on. We've never used MS SQL before. From
> what I've read, it seems like ADO requires a login/password to connect
> to it.
> Problem is, the customer doesn't have this piece of information, and
> although customers own the data, we don't want to ask the company that
> built the main application because our add-on does something similar
> to what they do (but better :-)).
> Is there a way to either bypass the login/password phase, or sniff it
> from the network? We just want to read data, not write anything to MS
> SQL.
> Thank you.
Or grant the Windows group that the connecting user belongs to the
same permissions that the other app is using.
Then from VB use "integrated security"|||On Fri, 6 Jul 2007 20:19:59 +0200, "Tibor Karaszi"
<tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:
>Have your DBA create a login using appropriate permission in the database and specify that login
I don't know if the customer even has admin access to their own MS SQL
server, but I'll ask.
Thanks guys.