Query Wizard works on one computer, but not another with same database

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

I have a database that was converted from Access 2000 to 2003. The
Query Wizard works fine on a computer that had Office 2K installed,
then upgraded to 2K3.

On a computer that has not ever had 2K installed, the query wizard
will not function properly. For example using the find duplicates
query wizard, the word query beside the radio button is missing. You
can still click on it and get the list of queries. When you click on
a table or query, it pops up with:

"You must select a table or query that contains at least one field
that does not have the Memo or OLE data type"

However if you open the same database on the computer that had 2000
installed, the query wizard works without error.

Anyone have any suggestions as to what may be missing or set
differently?
 
I have a database that was converted from Access 2000 to 2003. The
Query Wizard works fine on a computer that had Office 2K installed,
then upgraded to 2K3.

On a computer that has not ever had 2K installed, the query wizard
will not function properly. For example using the find duplicates
query wizard, the word query beside the radio button is missing. You
can still click on it and get the list of queries. When you click on
a table or query, it pops up with:

"You must select a table or query that contains at least one field
that does not have the Memo or OLE data type"

However if you open the same database on the computer that had 2000
installed, the query wizard works without error.

Anyone have any suggestions as to what may be missing or set
differently?
Click to expand...

Anyone have any ideas?
 
Hi Jeff,

I've never seen this problem, but the first thing I'd try is to
re-register the file ACCWIZ.DLL.

To re-register a DLL file,

1) Locate it (often it's 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.
 
Hi Jeff,

I've never seen this problem, but the first thing I'd try is to
re-register the file ACCWIZ.DLL.

To re-register a DLL file,

1) Locate it (often it's 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.
Click to expand...

The accwiz.dll file was in the C:\Program Files\Microsoft Office
\OFFICE11 folder. Dragged & dropped on regsver32.exe & successfully
registered it.

Still have the same problem. Any other suggestions?
 
Next thing would be to (1) make sure that the Office 2003 installation
is up to date (Service Pack 2) and (2) run Office Setup (from the
Control Panel add/remove programmes applet) and repair the installation.
 
Next thing would be to (1) make sure that the Office 2003 installation
is up to date (Service Pack 2) and (2) run Office Setup (from the
Control Panel add/remove programmes applet) and repair the installation.
Click to expand...

Office SP2 was deployed through WSUS. I'll try the repair from the
control panel & report back.
 
Office SP2 was deployed through WSUS. I'll try the repair from the
control panel & report back.
Click to expand...

The repair from the control panel fails, as does the repair from the
CD. Also the reinstall from the CD fails. Any ideas short of a
complete removal/reinstall?
 
A question I should have asked sooner: Create a new database on the
suspect machine. Create a small table and populate it with a few
records. Does the query wizard work?
 
A question I should have asked sooner: Create a new database on the
suspect machine. Create a small table and populate it with a few
records. Does the query wizard work?
Click to expand...
Sorry for the delayed response...
I created a new database with two tables, populated the two tables and
went to the query wizard again - same problem.

I then copied the database to the computer where the wizard works &
the wizard did work with the new database.
 
If it was a corporate machine in my care I'd have wiped the disk and
re-installed the image by now. If it's a home machine or the company
doesn't use a standard image, I might faff round checking versions of
ACCWIZ.DLL and various other files; but probably it's time for some
slash and burn.
 
Back
Top