thinglong.blogg.se

#Get ms access password how to
#Get ms access password code
#Get ms access password password

Since you can't use a trusted connection, this is the safest way to do it.

#Get ms access password password

If the password were stored in any fashion, a miscreant could simply sit down at an unattended machine and open the database. Explain that this policy will deny an unauthorized user the ability to open the database from an authorized user's machine. Therefore they must provide their password each time they open the database. Inform the users your organization's security policy prohibits storing passwords. You can find an explanation of this behaviour here.

#Get ms access password code

If you don't want to expose the connection string that includes the PWD, you could as well initiate a connection from VBA and hide the code by delivering a MDE or just password protecting the code. Since Access remembers opened connections until you close it, even if you close the db, your other tables will now open without any fuss, even if no password is stored in the linked tables Connect string. Something like DCount("*", "ptqConnect") will do.

in the startup procedure of your app make sure you call that PTQ.

paste the connect string of into the PTQ Connect property, and make sure you add the PWD=something in it.

create a passthru queries "ptqConnect" and enter any fast SQL statement in it, like SELECT 1.

copy the connect string of one of your tables.If that is not suitable, here is a possible alternative trick, exploiting the fact that Access remembers all opened connections until the program is closed: The best solution is obviously to use Windows security.

#Get ms access password how to

3) Perhaps some other way how to link the SQL server tables into Access?.

I am aware keeping password in some config file, or stored obfuscated in application configuration should be considered lowering security, but this is acceptable for the given setup.

2) Store the SQL server user password at client side.

If I try to do this now, I get error that the user is connecting from untrusted domain. I am not sure how this could be done, given that the server PC does not recognize the user from client PC.

1) Configure the integrated security model so that the user can log on, being automatically authorized by his Windows login (ie, use "trusted connection").

I see there are several ways how to solve this: The users on server PC and client PC both log onto their local machines, ie their users are not verified on independent domain server. However, there's one nuisance that should be somehow solved: the Access regularly asks for the user password, when opening the Access database. So, the data are now moved, an SQL server user (for accessing only that particular database) created, and the tables are linked the Access database via ODBC connection.

The first stage is to move all the data from MS Access database to SQL server while keeping the Access forms and reports at the client. I am in charge for migrating old Access 2007 project to MS SQL server 2008 Express.