January 17, 2003 at 3:16 pm
This is driving me bananas. We have a very simple setup using Access as a front end with SQL Server 7.0 as the back end. We typically design the database in Access, then export to SQL Server, then link the tables back to the Access database. We've been doing this for years.
Yesterday, we put a new database out there in the usual fashion (as above) BUT when we access the database from its Access front end, no SQL Server ID/Password dialogue box appears, and the SQL Server data is immediately available TO ANYONE!
All previously created databases are working fine, with the ID/Password dialogue box popping up as expected.
I've been up and down both Access (Office 2000) and SQL Server 7.0 looking for why this could be happening and what to do about it. I even thought maybe it was a fluke so I created another database purely in SQL Server and linked it to an Access front end. I got the same result -- No ID/Password dialogue box -- the data becomes immediately available.
What am I missing here, and what do I do? Thanks in advance for your help on this.
Scott Susor
DBA, Texas Children's Cancer Center
Houston, Texas
Edited by - Scott Susor on 01/17/2003 3:17:55 PM
Edited by - Scott Susor on 01/17/2003 3:26:07 PM
January 17, 2003 at 5:32 pm
If you know what user it is logging in as change the password. Then it should fail and popup the login on Access. I think you will find somewhere along the way the User Name and password were saved in Access by the Save Password option that is normally on the dialog that pops-up.
January 18, 2003 at 9:08 am
Or maybe you've granted NT login access to the tables?
Andy
January 22, 2003 at 10:14 am
Well, thanks for the ideas but neither appeared to apply. I am the only "user" right now and the database was set up the same as all others.
Now I also have another problem. I can't get to any of the data in any of the databases within SQL Server. This was working OK Friday, but now when I do a "Return All Rows" in SQL Server it gives me a "query error." This happens for the new database and all previously created ones.
Could recently changing to Windows 2000 have anything to do with this? Or could it be an ODBC problem? Other ideas?
Scott
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply