Comments by Member 9428144

Member 9428144 12-Sep-14 10:18am View

This is just the type of strategy I was looking for - so thanks. However, I have recently discovered that my data may not be so neatly ordered. Meaning ds1 could have "Grapes Small Large" and ds2 could have "Grapes Large Small". So this needs to be "equal" in my business case. So each value (Small Med Large) needs to be evaluated separately between the two Grapes dataset entries.

Member 9428144 20-May-14 12:50pm View

Well - I already have a page like that but I didn't think to put it there. I'll give it a try and Accept the solution if it works. thanks

Member 9428144 20-May-14 12:02pm View

Yes thanks. I knew about this identity tag and I should have posted my entire scenario (sorry).
We are also avoiding having hardcoded passwords visible. We have a third-party application we call to get the password of our application ID. Once I have that password - I then call the Impersonate Class with the username and password. This way we avoid having that password visible in web.config.
I also know I can have an encrypted file reference in web.config which does conceal the password. But again - the third party application has the ability to change an account password on the platform - so we also want to avoid having to regenerate encrypted config files. Having a contained class/dll we can call is a great solution to all of this. But I want to avoid calling it every time the app hits Page_Load. Again - sorry my original question did not include all this context.

Comments by Member 9428144 (Top 3 by date)