Apr 18 2006, 02:22 PM
I hope I put this in the right forum. I have an access 2000 app that I am working on that connects to an SQL server backend. I can set this up with a DSN and linked tables no problem. However, the user is prompted when a form is open. I would really like to create a login form that would set the login information when Access is first open so it can be used until it is closed. I have looked at many posts concerning login forms on this site and others, but can't seem to put together what I need.
Apr 18 2006, 02:48 PM
Its prompted because you didnt save Login ID And Password by creating the link.
If you're linking a table, select the Save The Login ID And Password check box to save the information for the table in the current databaseso that users won't have to enter it. If you leave the check box cleared, all users must enter the logon ID and password every time they open the table in each new session with Microsoft Access.
Your SQL database administrator can also choose to disable this check box, requiring all users to enter the logon ID and password each time they connect to the SQL database.
Check also this link
out on best practices SQL Server Security.
Apr 18 2006, 02:56 PM
I think I have a solution. I didn't want to save the password as this app would be distributed to various machines with various users. I have found a workable solution in that I created a passthrough query that I run using autoexec. This will prompt for connection properties before any forms open, and after the user has entered the info, aren't prompted again. I still wish I could create a custom form to do this, but for now this works.
Apr 18 2006, 03:22 PM
Glad you find a workaround...
I am just wondering why you don't set the security along with the Windows envoirement login?
Apr 18 2006, 05:19 PM
Have you tried using windows Authenication instead of SQL Server login/password? Let Windows and SQL do the work for you.
Apr 19 2006, 07:20 AM
I guess I always thought that windows authentication was "less secure" or "not as good" as SQL server logins. I will look into it. In the meantime, if you guys have any handy dandy links you would like to post I would appreciate it.
Apr 19 2006, 12:05 PM
I would say that Windows authenication is as secure, but only if the security policy of the company is valid. If the company takes security serious, I would think it would be as secure as a SQL login.
Apr 19 2006, 12:24 PM
Well, here is the problem (I think) with going this route. I am hosting SQL server on my machine (small company), which is NOT the domain server. Is there any way I can still use Windows Authentication? Currently when I try to configure user's computers they cannot see the DB I need them to in their ODBC choices.
Apr 19 2006, 03:46 PM
I've got an extra desktop that I use as a development server and I allow others to use it using Windows Authentication without any problems. Have you selected SQL Server and Windows Authencation in the security tab?
Apr 20 2006, 07:33 AM
You probably have to add DOMAINNAME\Domain Users as a login group in SQL Server. I have a similar setup, and it works fine.
Apr 20 2006, 07:44 AM
Which security tab are you referring to? Thanks for the info cfetch, I will try to look into that as well.
Apr 20 2006, 07:52 AM
Actually nevermind, I got it figured out and working. Thanks so much for the help! o!
Apr 20 2006, 02:38 PM
I have a custom logon form into sql server using vb.net. Sql Server LogOn Screen
This namespace returns a connection back to the calling program.
You could use that as a sample to create one in ms access.
If you don't have vb.net, I put the code into word and you would be able to see it.
Let me know.
Apr 21 2006, 10:05 AM
You are welcome.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here