Good morning Access Professionals,
I have posted this question in some other forums - I am casting a wide net because I need some good advice.
We have recently upgraded from SQL Server 2008 to 2014 two days ago and the smoke has finally settled. I thought about making a post about the pit-falls (error 44447 and 44446) but since there are NO entries on this forum or any other I frequent I figured it was so infrequent it wouldn't be worth it.
While I was making the DSN for my App, I chose the SQL Server Native Client 11.0 driver and it worked like a charm on my computer but when I deployed it, no one else could use it. It appears that when IT installed SSMS on my machine, the 11.0 driver was installed and no other machine has it.
I changed the driver to the generic SQL driver and all is right in the world.
My question is this, is it worth my time and effort trying to get IT to push this driver to everyone or should I just leave well enough alone?
We are currently using Win 10 64 bit / Office 2013 32 bit. Our IT department are contractors from General Dynamics and the meet any suggestions like this as an all-out attack on cyber security and my argument is going to have to be ultra-compelling.
The fact that it is working as-is will work against just about anything I can come up with so I am hopping to get some pearls of wisdom from some of you.
Is the juice worth the squeeze?
Posted by: wrmosca <wrmosca@comcast.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar