Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2078
  • Last Modified:

Upsizing wizard error - The table was skipped, or export failed but works on access template db

I am using the upsize wizard from Access 2000 database to SQL Server 2000.  When I try upsizing the DB from my client the report I get back just says "The table was skipped, or export failed."  I am running under Windows 2000 Professional OS, Office 2000 Premium.   I can import from the client’s DB from a SQL DTS but want to use the Access upsizing tool.

I even installed all the items from the article http://support.microsoft.com/kb/272384#kb1   except the  files ACWZ_Admin.msp and MDT2_Admin.msp which give errors when applying the update patch that the program is not installed or incorrect version.

If I use a template DB created from Access like expenses it all upsizes OK.


AGHH!
0
HometownComp
Asked:
HometownComp
  • 4
  • 3
1 Solution
 
flavoCommented:
Does the table have a PK?
0
 
HometownCompAuthor Commented:
how can I tell?
0
 
HometownCompAuthor Commented:
Some tables have primary keys.  I even tried creating a new table and that will not go up either.  I get the same error. - "The table was skipped, or export failed"
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
Leigh PurvisDatabase DeveloperCommented:
I'm puzzled by the line
"I can import from the client’s DB from a SQL DTS but want to use the Access upsizing tool."

Why don't you want to use the powerful and very often more reliable method of upsizing?
0
 
HometownCompAuthor Commented:
Is the more reliable method using DTS in Enterprise Mgr. to import into SQL 2000, adding in the pks which SQL doesn't seem to bring in ? (although I would just use SQL query analyzer to script any changes)
0
 
Leigh PurvisDatabase DeveloperCommented:
To my mind, upsizing is such an important task that I don't mind manually verifying the PK's afterwards.
I want to make sure that everything is spot on.

I suppose if you wanted - you could do it in advance offsite in development - and then generate the script to create the SQL database, run that at your client's office and use DTS to just import the data from the client's mdb - nothing more.

Then you're not spending lots of time onsite faffing about.
0
 
HometownCompAuthor Commented:
OK. then It looks like I will import using SQL DTS, then write scripts to create pks, build the database thru script, and then import the data.  Thoughts?

Any comments on when importing tables with the Access text type SQL autochanges them to nvarchar (2 bytes ) instead of the varchar (1 byte unicode) ?   They can just be left in the nvarchar type.  Thoughts?
0
 
Leigh PurvisDatabase DeveloperCommented:
Well - once you've done a test upsize - you can add the PK's through Enterprise Manager.
Once you're happy - let it generate a script to create the database - and then all you have to do is run that at your clients - and then run DTS to import the data.

As for nvarchar - it's just Unicode support.
If you have no need at all for the extended set that is permitted then you don't need it.
Many people use them though.  (Many don't too ;-)
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now