You could just password protect your VBA code, but this is well-known to be
next to useless protection against anyone who wants to get at it.

What kind of "third parties" do you mean - people at your company, or anyone
?

You could at least limit your exposure by creating a read-only account and
only giving it the minimum access rights: only allow that account to run the
stored procedures and nothing else.

Or create some kind of "web service" to centralize the data access in one
place and just have the excel files load from a URL.

Or put your database code in a dll.



Tim


"NeilR" wrote in message
oups.com...
Can anyone give me an easy way to provide an excel spreadsheet to
third parties with command buttons that would import various "tables"
of data from SQL stored procedures, but without giving them my SQL
connection information - ie with the SQL connection data "hard coded"
into the command buttons but not visible to the user?