L
Lee Vance
I created a form with secondary datasources pulling from SQL Server.
Originally, my connection was setup using Windows Authentication. That posed
a problem for other users as they do not have privileges to the database.
The form is published to a SharePoint document library that others have
access to.
We created a SQL user that has privileges to the database. We want to use
that as the connection authentication rather than Windows Authentication. It
appears that when I created the connection, a System DSN was created as well.
I've gone in and switched the DSN from Windows Authentication to this new
user, but when I republish this form to the SharePoint document library, it
still tries to connect using Windows Authentication.
1) Is there something I need to do when publishing to update the connection
strings?
2) Is this SQL user name and password going to be exposed to other users at
any point?
Thanks, Lee
Originally, my connection was setup using Windows Authentication. That posed
a problem for other users as they do not have privileges to the database.
The form is published to a SharePoint document library that others have
access to.
We created a SQL user that has privileges to the database. We want to use
that as the connection authentication rather than Windows Authentication. It
appears that when I created the connection, a System DSN was created as well.
I've gone in and switched the DSN from Windows Authentication to this new
user, but when I republish this form to the SharePoint document library, it
still tries to connect using Windows Authentication.
1) Is there something I need to do when publishing to update the connection
strings?
2) Is this SQL user name and password going to be exposed to other users at
any point?
Thanks, Lee