Report Packages, DSN's, and You!!

[ComplexQry]

I have an issue, and I am not sure what the best solution is.

My current setup is 1 Model and 2 Packages.  My model is setup in a way that as soon as a field is added to the database it flows all the way through to the business view (select * from Tablename)(Shortcuts to Query Subjects for the Business Views).  Low Low maintenance, right?  The two Packages I have, 1 is confidential (every Query Subject) and the other is non-confidential (only non-confidential Query Subjects).

Problem with this...
The DSN used to connect to the database has the Confidential Username/Password.  So lets say a Non-Confidential Table has the business need to have a Confidential Field added to it.  Since I have select * from tablename and shortcuts done for the Business Views.  That Non-Confidential Table with the newly added Confidential Field that is in the Non-Confidential Package, is now there for use.  Major Security Issue.

My Question...
Can Packages utilize separate DSN's?  Basically in this case, the Confidential Package would utilize a DSN with the Confidential Credentials and the Non-Confidential utilize a DSN with Non-Confidential.  That way the DSN would account for any Security Issues.

My current setup is darn near maintenance free.  I would prefer to keep it that.  Any suggestions?

[rockytopmark]

"Can Packages utilize separate DSN's?"

Not sure I totally understand the question, but in short, sure. 

If you need to have a Query Subject be sourced from 2 different Data Sources, depending on something like a role, group, etc, you can use macros to create this dynamic connection.