Upsize to sql server overrides sql server default location--why?

[Al]

I just recently upsized an Access DB using all the "defaults" which allows
Access to create, populate, as set up relationships etc, on one of our SQL
2005 Enterprise Servers.

The SQL Server default file location is on the E-drive. When the upsize ran
it created the database on the C-drive of the SQL server overriding the
default--which has created a lot of issues as you can imagine.

Anyone know how Access cab overrude the SQL server location default? I do
not ever want to see this happen again.

Thanks for you replies!!

 

[Sylvain Lafontaine]

Why don't you create and use an empty database as the target for the
upsizing?

 

[Al]

In retrospect that is probably what I should have done.

What I have found though is if I let Access "do it all" then all the
attributes and relationships build completely.

I'm just don't understand how it could override the DB defaults--which is
troubling.

 

[Sylvain Lafontaine]

Don't ask to much from the upsizing wizard or the migration assistant. You
can see them only as the very first step of upsizing a MDB database to
SQL-Server, nothing more and many people won't even use them at all when
performing an upsizing.