Well, it's been a while but I've got a question I just can't answer (even with searching this site, Google and msdn)
I have an Access 97 dB (well, about 30 dBs actually) that I didn't write (pretty standard story really) which is connected via DSN to an AS400. That link works great. I need to remove those and hook them up to the corresponding tables in our SQL Server 2000 instead. This is simple to do intitally. My problem is, the next time the dB is opened, it's asking the user for their SQL Server name/pwd.
I've tried hardcoding the userID/pwd into the file DSN, no dice. I've even tried to reattach the AS400 tables (just for grins) and I still have the problem of it asking for my pwd every time (which it doesn't do on the established links. The person who set this up is gone (of course) and was apparently deathly allergic to documentation...
Is there some trick I'm missing to getting the database to read the file DSN, or some other way to do this?
To answer, no, we're not using Windows authentication. Yes I know what it is, why it's good, why it's bad, and why it likes pink elephants. No, I can't just switch to pass through queries or do it all via code. Yes it's better, and eventually I will switch them all over. But I need to switch the tables now, not spend 3 weeks writing all these queries/code for all these databases, inevitably missing one or two and wreaking all sorts of havoc. I hate using DSNs to link to the server, but such is life. Until I have time to rewrite all thes dBs, I've gotta live with their design.
Thanks in advance for any and all suggestions...
Kyle
I have an Access 97 dB (well, about 30 dBs actually) that I didn't write (pretty standard story really) which is connected via DSN to an AS400. That link works great. I need to remove those and hook them up to the corresponding tables in our SQL Server 2000 instead. This is simple to do intitally. My problem is, the next time the dB is opened, it's asking the user for their SQL Server name/pwd.
I've tried hardcoding the userID/pwd into the file DSN, no dice. I've even tried to reattach the AS400 tables (just for grins) and I still have the problem of it asking for my pwd every time (which it doesn't do on the established links. The person who set this up is gone (of course) and was apparently deathly allergic to documentation...
Is there some trick I'm missing to getting the database to read the file DSN, or some other way to do this?
To answer, no, we're not using Windows authentication. Yes I know what it is, why it's good, why it's bad, and why it likes pink elephants. No, I can't just switch to pass through queries or do it all via code. Yes it's better, and eventually I will switch them all over. But I need to switch the tables now, not spend 3 weeks writing all these queries/code for all these databases, inevitably missing one or two and wreaking all sorts of havoc. I hate using DSNs to link to the server, but such is life. Until I have time to rewrite all thes dBs, I've gotta live with their design.
Thanks in advance for any and all suggestions...
Kyle