If you create a user control (.ocx) by using Microsoft
Visual Basic, and then you embed the control in an Excel document or a Word
document, when you try to save or print the document, you may receive an Access
Violation. This problem may occur if the default printer that is installed is a
network printer that has a share name of more than 19 characters.
The problem occurs because the DEVMODE structure in
Msvbvm60.dll was corrupted during ANSI/UNICODE conversion. The corrupted
DEVMODE is sent to the printer driver, which causes the Access Violation.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. Note
You must have a Visual Studio license agreement to obtain this hotfix.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of
this fix has the file attributes (or later) that are listed in the following
table. The dates and times for these files are listed in coordinated universal
time (UTC). When you view the file information, it is converted to local time.
To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time tool in Control Panel.
Date Time Version Size File name Platform
17-Jul-2002 05:36:22 22.214.171.124 1,392,640 Msvbvm60.dll i386
To work around this problem, do either of the following:
- Shorten the printer share name to less than 19
- If it is available, use the printer driver that is included
with the version of Windows that you are using and that is suitable for your
printer. In some cases, this has prevented the problem.
Microsoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.