Access 2002 (Office XP) text import wizard broken/not found

[Ray Adams]

Upon several attempts to import a text file, the following message is received:

Microsoft Access can find the wizard....wizard not installed...incorrect
setting in the Windows Registry...wizard disabled.

I have checked the list of disabled features, none exist.
I have followed the recommendations of article 290068, highlighting a
similar problem, and found the registry setting to already be as suggested.
I am not attempting to import an Excel file, nor have I gotten far enough
with the wizard to incur the field renaming issue, for which the popular fix
is to contact Microsoft to receive the post SP-3 hotfix.

It is 12:00 midnight on a Saturday, and unsolvable problems like this is
what causes me to lose faith in Microsoft products. There has to be a
solution for this somewhere online.

Any ideas??

 

[Ray Adams]

CORRECTION:
2nd line should read:
Microsoft Access CANNOT find the wizard...wizard not installed...incorrect
setting in the Windows Registry...wizard might be disabled.

Help is still needed on this issue.

 

[John Nurick]

Hi Ray,

These steps usually solve problems like the one you describe:

If the import/export wizards don't work at all, or if you get "No object
in this control" re-register ACCWIZ.DLL.

If it's one or more file formats that aren't listed, re-register the
following files
msexcl40.dll (Excel)
msxbse40.dll (dBase)
mspdox40.dll (Paradox)
mstext40.dll (Text, CSV, tab-delimited))
In Access 97, the filenames contain 35 instead of 40.

To re-register a DLL file,

1) Locate it (usually all these are in the Windows\System32 or
WINNT\System32 folder.

2) Locate the file regsvr32.exe.

3) Drag the DLL file's icon onto the regsvr32.exe icon.

 

[Ray Adams]

John,

Thanks for your reply. Sorry, your recommendations did not resolve this
problem.

Although the mstext40.dll and regsvr32.exe files were found in the
\Winnt\system32 folder, the ACCWIZ.DLL was found in the \Program
Files\Microsoft Office\Office10 folder. As the drag-n-drop operation was
taking much too long, I copied the ACCWIZ.DLL file to the \Winnt\system32
folder and registered it from the command line. The results were successful,
according to the popup message, but the failure still occurs when attempting
to import a text file.

Next suggestion?

 

[John Nurick]

Ray,

I don't understand what you mean by "as the drag-n-drop operation was
taking much too long". Do you just mean you found it inconvenient to
arrange the windows so you could see ACCWIZ.DLL and regsvr32.exe at the
same time, or did something strange happen - or not happen - when you
dropped ACCWIZ.DLL onto regsvr32.exe?

If the latter, I'd run a disk check and perhaps defrag the drive.

Either way, the next thing I'd try is to rename ACCWIZ.DLL and then run
Office XP setup and repair the installation.

 

[Ray Adams]

John,

The drag'n drop operation of your step 3 below was taking to long to happen:

To re-register a DLL file,

1) Locate it (usually all these are in the Windows\System32 or
WINNT\System32 folder.

2) Locate the file regsvr32.exe.

3) Drag the DLL file's icon onto the regsvr32.exe icon

I let a defrag run overnight, and will check on the outcome later today. I
will also try your next recommendation of deleting the file, running setup
again, and determining if a recreated file solves the problem. I hope it is
not a problem that the ACCWIZ.dll file was in the \Program
Files\Microsoft Office\Office10 folder, and not in the Windows folder
because it seemed to register ok anyway.

 

[Ray Adams]

John,

Cascaded two windows, one on the \winnt\system32 directory, and the other on
the \Program Files\Microsoft Office\office10 folder. Dragged the accwiz.dll
on top of the regsvr32.exe file, and everything looked ok, but the same
result occur when attempting to import a text file.
Yes, defragged multiple times today. System runs faster, but still no go
with the import.


Any ideas??

 

[John Nurick]

Only what I've already suggested: rename ACCWIZ.DLL and then run
Office XP setup and repair the installation.

 

[Ray Adams]

I also performed the rename and repair operation as you suggested. Results
remain the same.

More ideas??

 

[Ray Adams]

John,

Tried everything, including logging on as a network administrator, local
administrator, and local and network users. Access simply cannot find the
text import wizard.


Help, or I am going back to Office 2000.

 

[John Nurick]

I'm running out of ideas, but have realised that you haven't given an
exact description of the symptoms.

Please can you give an exact step by step description of what you do
when attempting to import a text file, starting from File|Get External
Data|Link and reporting the exact text and error numbers from any
messages you get.

 

[Ray Adams]

John,

Turns out the system did not have SP-2 installed, or the MSJET40.DLL file
was too old. Updating the the MSJET40.DLL file did correct the problem, but
so would have installing SP-2. Now the problem is more of the common one
reported where the subsequent fields/columns, are not being imported with
data. Column 1 is fine, but the remainder are flagged to be in error, not
imported, and dumped into a separate table indicated with a same indicative
of import errors.

Investigating other posts for resolution. Thanks for your help.