Sounds like the imported tables have rules or are set with different log in
permissions.
I'd look at your security setting for the issue.
"paxdominus" wrote in message
> Greetings,
>
> I have a large legacy Access 2002 database that connects to a SQL
> Server backend. As it stands, it connects fine. But, we're trying to
> upgrade to SQL Server 2005.
>
> We actually have tables from three different SQL Server databases as
> linked tables, and a multitude of local tables, so we have 3
> connections that we need to keep open. For the current database, I
> created a login form that takes allows the user to enter their
> username and password one time and it opens all three connections.
> When I change the code to accommodate the new 2005 server, the form
> seems to log in to the SQL Server side of things, but then when trying
> to access any of the linked tables, it pops up the Login to SQL Server
> screen.
>
> I checked the code and am able to pull properties of the linked
> databases, so I think that they are open, at least at that point. And
> I know that I can get to the tables, but I don't think that I should
> have to re-login after opening the database connection. Is there
> something different enough about connecting to SQL Server 2005 that
> would be screwing this up?
>
> Pax Dominus
>
FAQ
Search
Profile
Private Messages
Log in
