April 2, 2002 at 1:37 pm
I setup a File DSN to link SQL Server 7 tables to an Access 2000 front end application. The only problem I am having is that the login name keeps auto populating with the login I used to set up the connection. Is there any way to blank it out and set focus to the user name?
April 2, 2002 at 3:01 pm
I believe you can edit the file directly.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 2, 2002 at 5:57 pm
I tried to edit the file. The User ID is blank, but Access must be saving it somewhere else because it keeps pulling it up. If it doesn't have a name to pull up, it shows administrator as the login. Any more ideas? Thanks!
April 3, 2002 at 6:51 am
Then change it to something useless, this i what I did.
UID=EnterYourUserName
Now they even have a hint of what to do. Then you just copy the file dsn from machine to machine.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 3, 2002 at 8:05 am
This is a good work around. But, I was hoping to get rid of the extra step of deleting the auto-populated user name. This is an enterprise wide application. I'd hate to expect the users to do this on a daily basis.
April 3, 2002 at 10:15 am
You should be able to edit the Access system table that contains the connect string, why not just fix it there?
Andy
April 3, 2002 at 10:28 am
Which Access system table houses that information? I looked at the system tables and didn't see it anywhere.
April 3, 2002 at 11:00 am
MSysObjects in Access2K, look in the connect column.
Andy
April 3, 2002 at 11:04 am
Access won't let me change it. It's a read only table
April 3, 2002 at 4:15 pm
If nothing else you could rewrite you database forms to connect via ADO instead of linked tables (this is one step below writing a full vb app). Then you can use local tables to store the username and a form to collect the password (plus you can set focus and when they change the username it will update the table and make the username default last user). I don't think you can set focus on the links login otherwise anyway. Or you could write a form to open the File DSN check for EnterYourUserName and if there have them enter the updated correct name and if the name does not match does not have them enter the info.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 3, 2002 at 5:32 pm
You're right about the system table - will have to look more, seems like back when I used Access 97 a lot it was possible to alter it, but maybe I was just relinking programmatically? Have to dig for the code.
Maybe a better question is why would you want the user to enter a UID and password? Have you considered using NT security?
Andy
April 4, 2002 at 10:56 am
We want to make the database very secure. We don't want anyone to just walk up to a computer and have rights to the database. Also, we want to have the application timeout from inactivity - forcing them to login again.
April 4, 2002 at 12:10 pm
I'd say NT is better than SQL login for that. Require everyone to keep workstations locked when they are away, change passwords at scheduled intervals. NT is much less administration. Do you have reasons/requirements where NT won't work?
Andy
April 4, 2002 at 7:52 pm
I agree with Andy, NT Accounts would be better for you as you can then use trusted connections as long as they log intot the Domain or Server when they log into Windows. Now as for timeout we accomplished this by having a hidden form launch that had API code to catch key strokes and mouse movement then when stopped we started a timer to that when expired shut down Access (sorry I no longer have the code). You may if you need timeouts want to consider rebuilding your app in Web format thru ASP (this will also perform better than table Links in Access).
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 5, 2002 at 6:12 am
I was brought on to do a major overhaul to a really big, really bad Access database application. Phase 1 is to move the data to SQL Server because of all of the crashes we are experiencing. Phase 2 is to create a new application. We are going to use Access data projects because of its client server capabilities and speedy development environment - as I am the sole developer. This is my first time working for real in SQL Server, but I have played with it a lot for my own purposes. I've written ASP code before, so I know the pros and cons of using it. For their purposes, an Access ADP is the best solution.
Thanks for all of your help guys! It's been a real learning experience. I'll let you know how it goes.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply