June 24, 2013 at 8:17 am
I was planning to use the MSysConf table in a database to prevent MS Access from saving passwords to linked tables.
The client is using SS 2008 R2 and Access 2007 on Windows 7. I have been developing on Windows 8, using Access 2010 and my own dev install of SS 2012. My plan was to work out the code locally and then copy it into the client's dev environment for refinement and testing.
What I have found is that the desired behavior -- not saving passwords -- is exhibited on my own Win 7/Access 2010/ SS 2012 box, but NOT on the Win 8/Access 2010 box linked to the same SS 2012 instance.
I have several questions.
1) Is this something others have experienced?
2) Since the behavior differs, not by the SS instance, but by the client OS, am I wrong in looking at that as the problem?
3) What else could I be missing that would account for this behavior?
4) The obvious implication here, as I see it, is that this should work today on their Win 7 clients, but I am looking ahead a year or two and wondering what happens if they upgrade to Win 8 (and I know "upgrade" is a term not all might agree with)?
Thanks.
June 24, 2013 at 8:58 am
I should add that I haven't yet had time to investigate whether this is related to ODBC driver differences.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply