Don't want Trusted Connection option...

Hi,
Weird question, but hey!!
We have mixed-mode authentication on one of our databases.
Is there any way of avoiding the users seeing the "Use trusted connection"
option when in the connection dialog (eg from Excel Import Data)
I would like to enforce use of the Username/Password option if possible.
Otherwise, I'm faced with implementing user-level SQL Server security &
Windows authentication mode for an application which has, up until now, run
as the only available app in a very restricted desktop environment.
All suggestions gratefully received.
TIA
SteveSteve,
First of all security level is set at server level not per database. If I
understood you correctly, you want to use SQL Authentication for one
database and keep mixed mode for all other database
To stop user connecting to database using Trusted connection.
Deny BULITIN\Administrator account
make sure no windows user has permission on that database
create sql user account in that database
create dsn to use the new user name/password and use the new dsn to connect
to sql server
VT
"CyberDwarf" <steve.ingle@.furlongsolutions.com> wrote in message
news:Ory%23$IDIHHA.4804@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Weird question, but hey!!
> We have mixed-mode authentication on one of our databases.
> Is there any way of avoiding the users seeing the "Use trusted connection"
> option when in the connection dialog (eg from Excel Import Data)
> I would like to enforce use of the Username/Password option if possible.
> Otherwise, I'm faced with implementing user-level SQL Server security &
> Windows authentication mode for an application which has, up until now,
> run as the only available app in a very restricted desktop environment.
> All suggestions gratefully received.
> TIA
>
> Steve
>|||Thanks VT.
I was already working down that route, but it's nice to have my reasoning
confirmed
Steve|||You may be interested in the route we have taken...
a.. Create a project custom property to hold the (encrypted) connection
string;
b.. In VBA code, ensure that Persist Security info is turned OFF;
c.. Make sure sure that all Windows users have no rights to access SQL
Server (ie, they won't be able to use a Trusted Connection);
d.. When the ADE starts, we look up the required connection info from the
custom property, connect to SQL Server using the required access
permissions, then remove the Persist Security setting (the project loses the
password);
e.. At this point we have our required connection and no-one else can
access the backend via our ADE, unless they know the admin logon &
password).
That's basically it!
We've done basic testing & it seems to work...