Wrox Programmer Forums
|
Pro VB 6 For advanced Visual Basic coders working in version 6 (not .NET). Beginning-level questions will be redirected to other forums, including Beginning VB 6.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Pro VB 6 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old November 10th, 2003, 01:57 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 121
Thanks: 1
Thanked 0 Times in 0 Posts
Default Upsizing problem

I am having problems to upsize two Access 2000 databases to SQL Server 2000. For one database everything works OK except Access queries. The Upsizing Wizard does not convert an Access query to stored procedure (nor view or table). How to convert an Access query to SQL Server stored procedure? For the second database the Upsizing Wizard did not work at all. For each converted table the report shows up the reason: "table has been skipped". Without any explanation why?
I've tried to convert the Access database to SQL Server database using DTS. It works for importing all tables with the data but all relations and validation rules have been lost??? All Access queries have been converted to tables (not to views or stored procedures???).
Is there any smooth right way to upsize an Access database to SQL Server database?
     Thanks in advance
                       Dmitriy
 
Old November 11th, 2003, 11:44 AM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The upsizing wizzard will not convert queries to SQL SErver. You must convert them manually. also make sure that after upsizing the data to SQL Server you check all of your data types on your table to ensure that the proper datatypes have been used. Access sucks at doing this.

Read books on line on how to create stored procedures. In the meantime, you can create views on SQL server and link them to Access and filter them the same way on your front end. This will help you get started without too much of a headache to you and your users.

DTS does not create relationships. It only transfers date. It also does not upgrade your queries to views and stored procedures.





Sal
 
Old November 12th, 2003, 10:16 AM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 121
Thanks: 1
Thanked 0 Times in 0 Posts
Default

Thanks Sal,
I've got it already from the sites:
http://builder.com.com/5100-6388-5059624.html and
http://support.microsoft.com/?kbid=295231
articles. Yes, Microsoft is not "perfect". What is interesting the Oracle utility "Oracle migration workbench" to migrate data, all relations and constrains from Access database to Oracle is much better and smarter.

Thanks again,
          Dmitriy





Similar Threads
Thread Thread Starter Forum Replies Last Post
Arabic problem when use upsizing wizard naeem.net SQL Server 2005 1 June 3rd, 2008 02:33 PM
Upsizing. scandalous Access 0 February 5th, 2007 08:48 AM
Upsizing to MSDE2000A from Access2000 megasime999 SQL Server 2000 0 October 21st, 2004 10:55 AM
RE: Upsizing wizard sherr8 SQL Server 2000 3 June 12th, 2003 12:49 PM
RE: Upsizing wizard sherr8 Access 3 June 9th, 2003 11:34 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.