"There are no registered wizards of this type"

[Bill R via AccessMonster.com]

I copied an mdb to a file with a different name. Now, when I try to view the
code for a form I get the "There are no registered wizards of this type"
error msg. Forgive me for complaining, Mr. Gates, but how is it possible to
get a MS error msg and find no reference to it whatsoever in the MSKB?! Does
the left hand know what the right hand is doing over there in Seattle?
Anyway, I hope someone on this site can offer some insight.

Thanks,

Bill

 

[Bill R via AccessMonster.com]

PS.

There is also a lingering class module for a form that was deleted. When I
try to open it I get:

"Error accessing file. Network connection may have been lost."

 

[Jeff Conrad]

Are you using Access 2000 without SP3 installed by
chance? Is so read on.

I think you've been stung by a particularly nasty bug in
Access 2000. Sure sign is that dreaded "Network Connection
may have been lost.." message. Details about it can be
found here:

http://support.microsoft.com/?id=304548

The corruption in your database may not be recoverable.
You might try importing everything into another database.
I believe this bug is fixed with Service Pack 3, but it
will not *fix* corruption already present. To avoid this
bug you absolutely, positively, have to compile your
database EVERY time you import something.

Also, (from MVP Dirk Goldgar) one other thing you might
try first is decompiling your database -- or rather, a
copy of it. Instructions for how to do this may be found
here:

http://www.mvps.org/access/bugs/bugs0008.htm

and here:

http://www.granite.ab.ca/access/decompile.htm

This was also posted by someone from Microsoft:

326605 ACC2000: Issues Fixed in Access 2000 by Office 2000 Service Pack 3
http://support.microsoft.com/?id=326605

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

After applying Office 2000 sp3 you are going to need to salvage your
database modules (Standard, Forms/Reports) by saving them out to text
files. Example:

- Open Form/Report in design view and select menu option View > Code
- Select the menu option Edit > Select All (to select vba code)
- Select menu option Edit > Copy
- Paste in Notepad file
- Close VBA window to return to Form/Report
- Within the properties Window of Form/Report change the property "Has
Module" from "Yes" to "No"
(this will delete the code behind the object)
- Save your Form/Report
************* Repeat above steps for each Form/Report that has code
*****************
- For your Standard module just open and copy to text files

- Then import all your objects (within exception of your Modules) to a new
database file
- Copy the code from the above text files into new modules in your new
database
- For the Forms/Reports reverse the steps by opening their VBA modules and
pasting the code from the text files

*******************************
You can also try running decompile switch but the above methods are
normally your only shot..


I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access
Good luck,
--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html

in message:

 

[Bill R via AccessMonster.com]

Jeff,

Thanks for your response. I have recently had Office2003 installed on my PC
(not my choice). As you can see I'm developing in Access2k. It's the only 2k
program running on my PC. I'm guessing something in the 2003 dlls is causing
the difficulty. I haven't seen the dreaded msg since my posting, so I'm
hoping it's gone for good. I'm keeping this post just in case it rears it's
ugly head again.

Bill

Are you using Access 2000 without SP3 installed by
chance? Is so read on.

I think you've been stung by a particularly nasty bug in
Access 2000. Sure sign is that dreaded "Network Connection
may have been lost.." message. Details about it can be
found here:

http://support.microsoft.com/?id=304548

The corruption in your database may not be recoverable.
You might try importing everything into another database.
I believe this bug is fixed with Service Pack 3, but it
will not *fix* corruption already present. To avoid this
bug you absolutely, positively, have to compile your
database EVERY time you import something.

Also, (from MVP Dirk Goldgar) one other thing you might
try first is decompiling your database -- or rather, a
copy of it. Instructions for how to do this may be found
here:

http://www.mvps.org/access/bugs/bugs0008.htm

and here:

http://www.granite.ab.ca/access/decompile.htm

This was also posted by someone from Microsoft:

326605 ACC2000: Issues Fixed in Access 2000 by Office 2000 Service Pack 3
http://support.microsoft.com/?id=326605

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

After applying Office 2000 sp3 you are going to need to salvage your
database modules (Standard, Forms/Reports) by saving them out to text
files. Example:

- Open Form/Report in design view and select menu option View > Code
- Select the menu option Edit > Select All (to select vba code)
- Select menu option Edit > Copy
- Paste in Notepad file
- Close VBA window to return to Form/Report
- Within the properties Window of Form/Report change the property "Has
Module" from "Yes" to "No"
(this will delete the code behind the object)
- Save your Form/Report
************* Repeat above steps for each Form/Report that has code
*****************
- For your Standard module just open and copy to text files

- Then import all your objects (within exception of your Modules) to a new
database file
- Copy the code from the above text files into new modules in your new
database
- For the Forms/Reports reverse the steps by opening their VBA modules and
pasting the code from the text files

*******************************
You can also try running decompile switch but the above methods are
normally your only shot..

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.

Regards,

Eric Butts
Microsoft Access

Good luck,

PS.

[quoted text clipped - 9 lines]

 

[Bill R via AccessMonster.com]

Will installing Office2k SP3 in a Win2K environment, running Access2K and
Office2003 (minus Access) cause problems? What effect, if any, will the 2K
SP3 have on Office2003?

Are you using Access 2000 without SP3 installed by
chance? Is so read on.

I think you've been stung by a particularly nasty bug in
Access 2000. Sure sign is that dreaded "Network Connection
may have been lost.." message. Details about it can be
found here:

http://support.microsoft.com/?id=304548

The corruption in your database may not be recoverable.
You might try importing everything into another database.
I believe this bug is fixed with Service Pack 3, but it
will not *fix* corruption already present. To avoid this
bug you absolutely, positively, have to compile your
database EVERY time you import something.

Also, (from MVP Dirk Goldgar) one other thing you might
try first is decompiling your database -- or rather, a
copy of it. Instructions for how to do this may be found
here:

http://www.mvps.org/access/bugs/bugs0008.htm

and here:

http://www.granite.ab.ca/access/decompile.htm

This was also posted by someone from Microsoft:

326605 ACC2000: Issues Fixed in Access 2000 by Office 2000 Service Pack 3
http://support.microsoft.com/?id=326605

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

After applying Office 2000 sp3 you are going to need to salvage your
database modules (Standard, Forms/Reports) by saving them out to text
files. Example:

- Open Form/Report in design view and select menu option View > Code
- Select the menu option Edit > Select All (to select vba code)
- Select menu option Edit > Copy
- Paste in Notepad file
- Close VBA window to return to Form/Report
- Within the properties Window of Form/Report change the property "Has
Module" from "Yes" to "No"
(this will delete the code behind the object)
- Save your Form/Report
************* Repeat above steps for each Form/Report that has code
*****************
- For your Standard module just open and copy to text files

- Then import all your objects (within exception of your Modules) to a new
database file
- Copy the code from the above text files into new modules in your new
database
- For the Forms/Reports reverse the steps by opening their VBA modules and
pasting the code from the text files

*******************************
You can also try running decompile switch but the above methods are
normally your only shot..

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.

Regards,

Eric Butts
Microsoft Access

Good luck,

PS.

[quoted text clipped - 9 lines]

 

[Bill R via AccessMonster.com]

PS. Access2K is the only Office2K program I am running.

Are you using Access 2000 without SP3 installed by
chance? Is so read on.

I think you've been stung by a particularly nasty bug in
Access 2000. Sure sign is that dreaded "Network Connection
may have been lost.." message. Details about it can be
found here:

http://support.microsoft.com/?id=304548

The corruption in your database may not be recoverable.
You might try importing everything into another database.
I believe this bug is fixed with Service Pack 3, but it
will not *fix* corruption already present. To avoid this
bug you absolutely, positively, have to compile your
database EVERY time you import something.

Also, (from MVP Dirk Goldgar) one other thing you might
try first is decompiling your database -- or rather, a
copy of it. Instructions for how to do this may be found
here:

http://www.mvps.org/access/bugs/bugs0008.htm

and here:

http://www.granite.ab.ca/access/decompile.htm

This was also posted by someone from Microsoft:

326605 ACC2000: Issues Fixed in Access 2000 by Office 2000 Service Pack 3
http://support.microsoft.com/?id=326605

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

After applying Office 2000 sp3 you are going to need to salvage your
database modules (Standard, Forms/Reports) by saving them out to text
files. Example:

- Open Form/Report in design view and select menu option View > Code
- Select the menu option Edit > Select All (to select vba code)
- Select menu option Edit > Copy
- Paste in Notepad file
- Close VBA window to return to Form/Report
- Within the properties Window of Form/Report change the property "Has
Module" from "Yes" to "No"
(this will delete the code behind the object)
- Save your Form/Report
************* Repeat above steps for each Form/Report that has code
*****************
- For your Standard module just open and copy to text files

- Then import all your objects (within exception of your Modules) to a new
database file
- Copy the code from the above text files into new modules in your new
database
- For the Forms/Reports reverse the steps by opening their VBA modules and
pasting the code from the text files

*******************************
You can also try running decompile switch but the above methods are
normally your only shot..

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.

Regards,

Eric Butts
Microsoft Access

Good luck,

PS.

[quoted text clipped - 9 lines]

 

[Jeff Conrad]

in message:

Will installing Office2k SP3 in a Win2K environment, running Access2K and
Office2003 (minus Access) cause problems? What effect, if any, will the 2K
SP3 have on Office2003?

Hi Bill,

Well there can always *possibly* be problems, but your particular situation
seems quite reasonable. There may be some shared files used in Access 2000
and Office 2003, but I'm not completely sure. Running multiple versions of
Access and Office is quite possible and many people already use this setup
to test different configurations. The general rule of thumb is to install from oldest
version to newest version and always select a Custom install. Then you can
select to install into different directories and opt to not uninstall previous versions.
IIRC, only one version of Outlook can exist on a machine, but I could be mistaken.

You might want to review these information links and KB articles on the subject
of multiple versions of Access/Office.

How to effectively run multiple versions of Access on the system:
http://www.granite.ab.ca/access/multipleversions.htm

How to install Access 97 and Access 2000 on the same computer:
http://support.microsoft.com/?id=241141

Information about running multiple versions of Office with Office 2003:
http://support.microsoft.com/?id=828956

How to run multiple versions of Office on one computer:
http://support.microsoft.com/?id=218861

How to run multiple versions of Office on one computer:
http://support.microsoft.com/?id=290576