phiren (4/6/2010)
Our department does not create or support those Access databases. Users can use Access to do whatever that they want to do with the data once they link to the SQL Server database. The company has hundreds and possibly more than a thousand different databases that the users have created on their own. So, putting any kind of code on the end user's side is not an option unfortunately.
In that case, I don't think you're going to accomplish what you're looking for.
So far as I know, anything database-level or server-level is going to be receiving a hash of the password, not the actual string. That makes parsing it for things like the company name virtually impossible.
You can set up policies for the passwords, but Access will just give an error, based on what SQL Server tells it, it won't turn that into something that they can use.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon