Upsizing a db to SQL db

[Jim Richards]

When I try using the Upsizing Wizard to upsize a database to SQL database, I
am unable to login because I get an error message which says: "Login failed
for user 'Jim Richards'. Reason: Not associated with a trusted SQL Server
Connection." I am using 'Windows Authentication' and I am entering my
Windows User Name and Password. How do I fix this please? Thanks in advance,
Jim Richards

[Erland Sommarskog]

[posted and mailed, please reply in news]

Jim Richards (JW********@satx.rr.com) writes:

When I try using the Upsizing Wizard to upsize a database to SQL
database, I am unable to login because I get an error message which
says: "Login failed for user 'Jim Richards'. Reason: Not associated with
a trusted SQL Server Connection." I am using 'Windows Authentication'
and I am entering my Windows User Name and Password. How do I fix this
please? Thanks in advance,

If you are entering a username and password, you are trying to login with
SQL authentication. When you use Windows authentication, you only check
Windows authentication, and then SQL Server checks whether the Windows
user you are logged in as, has access to log into SQL Server.

Unfortunately, I don't know the user interface you are using, so I cannot
say how you should specify Windows authentication in that particular
interface.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[Erland Sommarskog]

Jim Richards (JW********@satx.rr.com) writes:

Thanks Erland. Here is a snapshot where I run into trouble. Maybe this
will help. TIA, Jim.

Judging from that interface, it seems that it only supports SQL Server
authentication, so you may need to enable that on your server.
But maybe you should ask around in comp.databases.ms-access. I don't know
Access, and thus I don't know the upsizing wizard either.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[DCM Fan]

OVerflows are caused in teh Upsize process when dates out of SQL server's
supported range are entered. Access has a much lower floor than SQL Server for
date ranges. datetime types only go down to the year 1753, and sna
smalldatetime goes down to 1900.

Access allows dates in the years 100!

Check that first.

This has nothing to do with your login, BTW.