Microsoft Knowledge Base Email Alertz

(295739) - When you import to or export data from a Microsoft Access database, the SQL Server Data Transformation Services (DTS) Designer or the Import/Export wizard may seem to stop responding (hang), and then exit prematurely. When you are working in the DTS...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 295739 - Last Review: November 14, 2003 - Revision: 3.2

BUG: DTS Designer May Stop Responding When You Use Microsoft Jet 4.0 OLE DB Provider

This article was previously published under Q295739
BUG #: 209139 (SHILOH)

SYMPTOMS

When you import to or export data from a Microsoft Access database, the SQL Server Data Transformation Services (DTS) Designer or the Import/Export wizard may seem to stop responding (hang), and then exit prematurely. When you are working in the DTS Designer, you may encounter this problem when you retrieve properties by right-clicking the Transform Data Task arrow. The Import/Export wizard just disappears from the monitor.

CAUSE

The symptoms exposed by this problem are caused by an unhandled access violation that occurs when information is retrieved from the IDBSchemaRowset object of the Microsoft Jet 4.0 OLE DB Provider.

WORKAROUND

As a workaround, change the values set to (NULL) in the SELECT list to a another value such as EMPTY, depending on the requirements of your application.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

MORE INFORMATION

This behavior may occur when the Microsoft Access database contains a UNION query similar to the following:
SELECT DISTINCT
     ID,
     C1,
     C2,
     C3
FROM T1
UNION ALL 
SELECT DISTINCT
     ID,
     C1,
     C2,
     (NULL)
FROM T2;
				
The problem exposes itself due to the default (NULL) value in the SELECT list of the UNION queries.

APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft OLE DB Provider for Jet 4.0
Keywords: 
kbbug kbfaq kbpending KB295739
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate