Hi all,
been a while since i've managed file dsn's based on network drives to connect access to sql server.
what i need from this.....
i want my db to use a file dsn that logs in users to the db tables without having to reconnect, without having to enter a further password (I have my own database securities in place) and to connect to my data using the file dsn located in a server folder (bit of a mouthfull!!!)
ok, our setup,
we have a sql server 2000 that has dual security access (windows and sql) and i have setup a SQL user that has got full access to the database that i need (and also has the database setup as its default database).
I have checked all tables have keys (so are updateable) so there should be no error with the tables.
I have created a file dsn through odbc pointing to the sql server, entered my user and password in for that user....
when in access and try to add linked tables using an odbc source and point it to the dsn file on the network it picks up the basic details to do with the sql server and db but seems to leave out the password, or simply changes the user to the one logged in on windows....
i thought file dsn's were good in the way that it remembered the user and password i wanted and would connect from any of the network pc's i started it up in without having to have a specific machine / user dsn setup or having to relink for each machine.
If someone knows more on this than me (which is probably not hard) and can point me in the right direction, or if you can suggest a better way to do this please drop me a note.....
infact if i could get around using odbc and get straight into the data tables that would be better.... although i cannot remember if access is willing to do that!!!
cheers
daveJam
even my shrink says its all your f#@/ing fault
been a while since i've managed file dsn's based on network drives to connect access to sql server.
what i need from this.....
i want my db to use a file dsn that logs in users to the db tables without having to reconnect, without having to enter a further password (I have my own database securities in place) and to connect to my data using the file dsn located in a server folder (bit of a mouthfull!!!)
ok, our setup,
we have a sql server 2000 that has dual security access (windows and sql) and i have setup a SQL user that has got full access to the database that i need (and also has the database setup as its default database).
I have checked all tables have keys (so are updateable) so there should be no error with the tables.
I have created a file dsn through odbc pointing to the sql server, entered my user and password in for that user....
when in access and try to add linked tables using an odbc source and point it to the dsn file on the network it picks up the basic details to do with the sql server and db but seems to leave out the password, or simply changes the user to the one logged in on windows....
i thought file dsn's were good in the way that it remembered the user and password i wanted and would connect from any of the network pc's i started it up in without having to have a specific machine / user dsn setup or having to relink for each machine.
If someone knows more on this than me (which is probably not hard) and can point me in the right direction, or if you can suggest a better way to do this please drop me a note.....
infact if i could get around using odbc and get straight into the data tables that would be better.... although i cannot remember if access is willing to do that!!!
cheers
daveJam
even my shrink says its all your f#@/ing fault