Access v MSSQL When to make the change

From memory, when you use the upsizing wizard, it does not always copy across the primary and foreign keys (ie, your relationships).

After you create the tables in SQL, you might need to go through and re-assign your keys.

Then insert the data.

Then go through the necessary columns and make those that were 'autonumbers' in Access, Identity fields in SQL Server.

This was an issue a few years ago anyway. MS released an office update called the 'Access 2000 upgrade to SQL Server 2000 Readiness Update" or something similar, so make sure you have that first.

Cheers,
Andrew

u kidin only 50mb ur db ? mine 1000mb+ and i m trying to upgrade for week now but keep geting errors and stuff :(

my qustion/problem is  :

i cleard the old topics and stuff ..  i compect and fix it and now my db 60mb.

now i am trying to do the Upsizing thing and it works for over 5 hours now

thats how it works ?

(ppl who can come help me little in chat /msn/icq plz send me pm  )

Access is a front end/IDE/distibution environment  for a data base engine. People tend to call the data base Access. The current data base used by access is Jet. It's one of many data base engines Access has been bundled with over the years.

Jet is very good for small workgroup applications built around LANs. However, it doesn't scale well for internet use. For LANs, once the capabilities of Jet are outgrown, it's a pretty good leap to MS SQL Server for most small companies.

Microsoft is phasing out the Jet Engine. Future versions of Access will be released with MSDE (MS SQL "Light"). You can use Access today to build and run applications with MSDE as the DB. The problems (IMHO) however, are that the SQL supported by Access is not optimized for the SQL supported by MSDE/MSSQL, and that the distibution methods to employ an Access/MSDE solution are cumbersome and eror prone.