Has anyone had problems with ODBC Conn. when changing from 2K to 2

[Todd]

We created an Access database and linked tables from a SQL 2000 server. ODBC
was setup and evrything was working fine using office 97 & 2000.

We recently upgraded to office 2003 and for some reason we are having
access/login problems with the Access DB.

For example, it wants the user to log in to every time you change from one
table to aonther. Used to be I logged in when I tried to access the first
table and I was good for the rest of the session.
Sometimes it comes up with the users name in the log-in, instead of the
default used in setting up ODBC.

Yet other times I open the database and after Access has opened the database
I am presented with a 'can not find database at path'. I continue to use
the database, but I would like to know why I am getting the errors.

If anyone could help, I would appricate it.

Todd

 

[aaron.kempf]

I would reccomend using an Access Data Project instead of stupid little
MDB.

MDB isn't a practical solution for anyone but these developers are too
fat and lazy to learn ADP.

MOVEON; mdb is completely obsolete; and it has been for almost a
decade.

i only have to set my user information once-- on the database server
via Windows authentication.

MDB is impossible to secure; but if you try to secure it you have to do
it in like 3 different places