Visual Studio 97 Service Pack 2 Readme

This article was previously published under Q172610
This article has been archived. It is offered "as is" and will no longer be updated.
This is a copy of the Visual Studio 97 Service Pack 2 Readme (Englishlanguage version).
Microsoft Visual Studio 97 Service Pack 2 Readme------------------------------------------------The Microsoft Visual Studio 97 Service Pack 2 Readme contains the followingsections: - Microsoft Visual Studio 97 Service Pack 2 provides an overview of Visual   Studio Service Pack 2. - Installing the Microsoft Visual Studio 97 Service Pack 2 provides   installation and setup instructions. - Notes on Fixes in the Visual Studio 97 Service Pack 2 provides overall   information on the fixes and the interactions with other products. - Finding More Information on Issues Resolved with This Service Pack   provides instructions on how to search online for the Knowledge Base   articles, and a list of the fixes and their summaries. - Welcome to Visual Basic 5.0 Service Pack 2 contains the Visual Basic   Readme for this Service Pack.Microsoft Visual Studio 97 Service Pack 2-----------------------------------------The Microsoft Visual Studio 97 Service Pack 2 includes all of the fixes inService Pack 1 and upgrades the following Visual Studio applications: Microsoft Visual Studio 97 (Professional and Enterprise Editions) Microsoft Visual Basic, version 5.0 (Professional and Enterprise Editions) Microsoft Visual C++, version 5.0 (Professional and Enterprise Editions) Microsoft Visual InterDev Microsoft Visual J++, version 1.1 Microsoft Visual SourceSafe, version 5.0 Microsoft Visual FoxPro, version 5.0 Microsoft Developer Network (MSDN) LibraryThese Visual Studio applications should be shut down before installing thisService Pack. Install this Service Pack whenever you have updated orchanged any of the applications in Visual Studio to ensure that you havethe latest fixes.Installing the Microsoft Visual Studio 97 Service Pack 2--------------------------------------------------------To install the Service Pack, insert the compact disc into your computer'sCD-ROM drive. If you have downloaded and decompressed the Service Pack, orif the Service Pack Setup does not automatically launch, go to the rootdirectory of the Service Pack and run Setup. The setup.exe will detect thelanguage of your computer's operating system and run one of the followingsetups: \fra\setup (French) \deu\setup (German) \enu\setup (English) \jpn\setup (Japanese) \esp\setup (Spanish) \kor\setup (Korean) \chs\setup (Simplified Chinese) \cht\setup (Traditional Chinese) \ita\setup (Italian)The Service Pack Setup detects any installed Visual Studio applications andthe specific languages those applications use. (Files are checked forlanguage, determined by the operating system settings and the individualfile settings.) This Service Pack supports the following languages: Czech,English, French, German, Italian, Japanese, Korean, Portuguese, Russian,Simplified Chinese, Spanish, and Traditional Chinese.During the installation, the Service Pack displays the files to beinstalled or updated based on the installed applications detected. Afterupdating your installation of any of the Visual Studio applications, theService Pack appends any actions to the VS97SP2.log file, which is storedin the root directory of the drive where Windows is installed. If you runthe Service Pack again, any additional file updates are appended to the endof the log file.Determining the Files That Setup InstallsSetup does not install all the files included in this Service Pack on yourcomputer.If the file does not exist already on your computer, in most cases Setupwill not install an update for it. Setup does not make any entries in thelog for files that are not present.If the file on your computer is a more recent version than the one in theService Pack, Setup will not update the file on your computer. The setuplog will state "File is up to date" for each file on your computer that isthe same version or more recent than what is on the Service Pack.Some .cab files are included in the Service Pack for redistribution only.Setup does not install them as part of the product update. You must copythem from the compact disc as needed.Interpreting the Setup Log FileSetup will perform one of two actions for each file in its file list. IfSetup detects that a file is not installed on your computer and the file isnot required, Setup will neither install it nor create a report in the log.Otherwise, Setup will report in the log one of the following conditions foreach file in its list: - "Copied successfully": The file on your computer was successfully   updated with the file in Setup's list. - "Rename on reboot": The file on your computer was in use during the   copy process. It will be replaced with the Service Pack copy on the next   system reboot. - "File is up to date": The Service Pack file contains version   information and the file on your computer is the same or a later   version. (Setup will also report this message if the date of any file   that does not contain version information, such as a text file, on your   computer is later than the date of the Service Pack file.)All other errors, such as "Access denied" or "The system cannot find thepath specified," are the operating system's error message for a particularproblem. These errors indicate that Setup could not update the file.Updating Files You Previously ModifiedThe primary way Setup determines which files to replace is by checking theversion information in a file's resources. However, some files, such astext files and non-binary files, have no resource information. In thesecases, Setup uses the time stamp to determine which files need to bereplaced.If you have altered the time stamp on any of the Visual Studio componenttext files or files that do not have version information, then Setup maynot replace those files. Source files and header files are examples of somefiles you might have changed.  Please check the setup log to determinewhich files have been updated. You must evaluate each of the files that isnot updated to determine whether you should use the Service Pack version.Determining the Update History of the Products Based on File VersionsTo determine which updates have been made since the initial release of aproduct, you will need to examine the version number in the properties ofone or more files.To determine the update status of a product:1. Look in the table below to determine which file you want to examine. In   some cases, you may need to examine more than one file to determine   fully the product's update history.2. For each file, right-click the file in Windows Explorer, then click   Properties.3. Click the Versions tab and compare the version listed with the version   in the table.The following table lists the developer tools that shipped in 1997 and havebeen updated in a Visual Studio 97 Service Pack. It also lists the keyfiles you should check to ascertain version information:                                       Version on   Product               Files         Release     SP1         SP2   -------------------------------------------------------------------   Visual Basic 5.0      setupwiz.exe  5.00.3716   5.00.3905   5.00.3905                         vb5ide.dll    5.00.3724   ---         5.00.4319   Visual C++ 5.0        link.exe      5.00.7022   5.02.7132   5.02.7132                         eecxx.dll     5.00.7122   ---         5.00.7198   Visual InterDev 1.0   devisws.pkg   5.00.7022   5.00.7087   No update   Visual J++ 1.1        devjava.pkg   5.00.7022   5.00.7128   5.00.7128                         devdbg.pkg    5.00.7022   5.00.7128   5.00.7198   Visual SourceSafe 5.0 ssscc.dll     5.00.2218   5.00.2219   5.00.2220   Visual FoxPro 5.0     vfp.exe       Build 402   No update   Build 412NOTE: "No update" means that the product has no updates in the ServicePack. Also note that even for updated products, some of the files did notchange from one service pack to the next.The InfoViewer tool is used to display online help for Visual Studio andMSDN. It has also been updated several times.               Version on   Files       Release     MSDN April  SP1         MSDN July   SP2   ---------------------------------------------------------------------   ivauto.dll  5.00.7022   5.00.7022   5.00.7055   5.00.7055   5.00.7198   deviv.pkg   5.00.7022   5.00.7022   ---         5.00.7022   5.00.7198Uninstalling the Visual Studio 97 Service PackThe Service Pack cannot be uninstalled independently of the product toolsbeing updated. To uninstall the Service Pack updates to a Visual Studio 97tool, such as Visual C++ or Visual Basic, you must uninstall the tool. TheService Pack updates will be uninstalled with it. Then, reinstall the toolswithout the updates.Because many interdependent components of the Visual Studio 97 tools aresimultaneously updated by the Service Pack, the products may becomeunstable if you roll back of some of the updates, or if you run Setup inmaintenance mode from the original product compact disc. This instabilitycan occur because of the combination of files that are updated and filesthat are not updated.To avoid an unstable combination of updated and old files, you must removeall of the Visual Studio 97 tools completely if you want to remove theService Pack updates or if you want to remove parts of the product. If youhad not installed everything in your Visual Studio suite before applyingthe Service Pack and you now want to add some of the remaining components,make the additions first, then apply the Service Pack.Notes on Fixes in the Visual Studio Service Pack 2--------------------------------------------------Microsoft Visual Studio 97 Service Pack 2 includes all of the fixes inService Pack 1.NOTE: Do not use the Microsoft Utility RegClean 4.1 with Visual Studio orany Visual Studio Applications.If you run RegClean 4.1 (build 97.71), you might find (if you have VisualC++ Enterprise or Visual Basic Enterprise installed) that the DatabaseDesigner no longer works, or (if you have Visual InterDev installed)the Database Designer and LinkView tools no longer work. If you have runRegClean, then reinstall the Visual Studio applications as appropriate.Active Server Pages (ASP) Browser Component Does Not Recognize the BrowserIf you are installing a new release of Microsoft Internet Explorer orNetscape Navigator, the ASP browser component object may not work in VisualStudio. The string identifying the browser may not be present in thebrowsecap.ini file, which is located on the Web server. The solution is toeither manually change the file or download a newer version of the filefrom the Internet Information Server (IIS) Web site.The version of the browsecap.ini file that currently ships with the VisualInterDev server components does not recognize Microsoft Internet Explorer3.02 as a valid browser. This results in an error when running an .asp pageusing the browser component in Microsoft Internet Explorer 3.02.An updated version of the browsecap.ini file as well as a 1.0b updatedversion of Active Server Pages is available at: Once there, click the "get IIS" button andchoose "Other free software," then "Updates for IIS." Choose a newcompressed or uncompressed browsecap.ini file to download.A full download of Active Server Pages English 1.0b is available under "getiis" as well. The 1.0b English version provides full DBCS enabling and somefixes.Updates to SQL Server and Visual Database ToolsYou must download SQL Server Service Pack 3 for working with VisualDatabase Tools and/or Visual InterDev.The SQL Server Service Pack 3 is available at: Server Service Pack 3 fixes several issues with the relational engineof Visual Database Tools including: - A query with two or more RIGHT/LEFT OUTER JOIN clauses resulted in a   syntax error.  Now they parse correctly and generate the correct result. - Some "complex" queries and views with five or more tables would stop the   server.  This resulted in a TDS Protocol error and a subsequent stop of   Visual Studio. This issue has been corrected.Visual Database Tools/Visual InterDev still requires, as a minimum, SQLServer Service Pack 1, but installing SQL Server Service Pack 3 isrecommended.Microsoft Internet Explorer Security Options and InfoViewerInfoViewer, the integrated online documentation viewer included with MSDNand Visual Studio, relies on the Microsoft Internet Explorer securitysettings for active content. The online documentation included with MSDNand Visual Studio includes some active content. If you set your MicrosoftInternet Explorer security's maximum security options while browsing theWorld Wide Web, some types of hyperlinks in your online documentation willnot work.Allowing Microsoft Internet Explorer to download an ActiveX control andthen automatically executing the downloaded code is a legitimate securityconcern. However, you can protect against this problem and still use theonline documentation included with MSDN and Visual Studio. To do so,complete the following steps.1. On the View menu in Microsoft Internet Explorer, click Options.2. Click Security.3. Make the following changes under "Active Content:"   a. Clear the "Allow downloading of active content" check box.   (This option ensures that no unknown active content will be downloaded   from a World Wide Web site.)   b. Select the "Enable ActiveX controls and plug-ins" check box.   (This option enables local ActiveX controls, such as those supplied with   MSDN and InfoViewer, to execute.)   c. Select the "Run ActiveX scripts" check box.   (This option allows local ActiveX scripts to execute.)4. Click OK.5. Restart Visual Studio.Special Instructions for Visual C++ for Microsoft Windows CECustomers of Visual C++ for Windows CE may experience problems with theVisual Studio family of products. If you want to install any part of theVisual Studio Service Pack, please uninstall Visual C++ for Windows CEfirst. If you encounter any problems using Visual C++ for Windows CE withVisual Studio, please call Visual C++ for Windows CE product support. Iffurther information becomes available, it will be posted on the web sitefor Visual Studio 97 Service Packs ( in the Knowledge Base (available on the web at Visual C++ .map FilesVisual Studio 97 Service Pack 2 updates the following .map files if youinstalled them in your system or system32 directory with Visual C++ 5.0.If you installed these .map files to a different location, used somederivative of these files, or used the .map files directly from the VisualC++ 5.0 compact disc, you will need to update these files manually orreference them directly from the Service Pack 2 compact disc. You can findthe Service Pack 2 updates to these files in the \all\vc\debug directory onthe Visual Studio Service 97 Pack 2 compact disc:  Mfco42ud.mapMicrosoft Transaction Server UpdatesThis Service Pack does not include any updates to the Microsoft TransactionServer. To gain access to the Microsoft Transaction Server service packsreleased since it shipped with the Enterprise Editions of Visual Studio 97,Visual Basic 5.0, and Visual C++ 5.0, go to  This site contains pointersto Microsoft Transaction Server 1.1 for x86, Service Pack 2 for DigitalAlpha, and the Microsoft Transaction Server SDK beta.InstallShield Express for Japanese Visual C++ 5.0The additional files required for the custom edition of InstallShieldExpress that is included with the Japanese release of Visual C++ 5.0 arenow available. Please refer to \jpn\IShield\readme.txt for details.Finding More Information on Issues Resolved with This Service Pack------------------------------------------------------------------The Microsoft Knowledge Base contains articles that provide more in-depthinformation about the Visual Studio issues that are fixed in this ServicePack. To locate these articles, go to and follow the instructions below to build a query.To build a Visual Studio Service Pack query:1. Choose a product. (In this case, click "Any Products.")2. Specify the type of search. This should be set to "Search the article   text."3. Enter the following as your search phrase:      VS97FixlistSP24. Click "Begin Search."Knowledge Base articles that contain VS97FixlistSP2 but do not containVS97FixlistSP1 describe fixes that were added in Service Pack 2. BecauseService Pack 2 includes all of the fixes in Service Pack 1, all of thearticles describing the fixes in Service Pack 1 will contain both keywordsVS97FixlistSP1 and VS97FixlistSP2. To find just those new items that werefixed in Service Pack 2, search for:    VS97FixlistSP2 and not VS97FixlistSP1For a file containing all of the text from all of the Knowledge Basearticles, look on the web site for Visual Studio 97 Service Packs: KB ArticlesService Pack 1 fixes some problems with saving samples to directories thatcontain high-ASCII characters in the path.Q168264   Copying Samples to a Dir with High ASCII Stops File I/OQ168265   Error "Microsoft Jscript error" After Copying SampleService Pack 2 fixes a bug preventing the download of samples with certainversions of Microsoft Internet Explorer. It also fixes a search results-related performance problem in which Developer Studio sometimes uses 100percent of idle time. The Service Pack fixes a bug that causes repeated"Merging keywords" for anyone who does not have administrator privileges inWindows NT. It fixes a limitation on the total number ofInfoViewer titles.Q171844   InfoViewer Cannot Download Samples if IE4.0 is InstalledQ171845   Results List Uses 100% of CPU on IdleQ171846   Limit on the Total Number of InfoViewer TitlesQ171847   Merging Keywords for Search Requires Admin PrivilegesVisual Basic 5.0 KB ArticlesFor a more thorough discussion of Visual Basic 5.0 fixes in Service Pack 2,go to the end of this file where the Visual Basic 5.0 Service Pack 2 Readmeis appended.The Service Packs address problems in dbgrid32.ocx, msrdc20.ocx, andmsrdo20.dll related to data-binding and other issues. Also included arefixes for the incompatibility problems with comctl32.ocx. There is also anupdate to the Visual Basic 5.0 Setup Kit and some of the .cab files for theActiveX component download. These .cab files are not installed by theVisual Studio Service Pack but are included on the Service Pack compactdisc.Q167122   FindItem Method of ListView Incorrectly Returns an ErrorQ167123   COMCTL32.OCX Is Binary Incompatible with Previous VersionQ167947   ODBC CAB File Does Not Install 16-bit ODBC FilesQ167948   Internet Component Download Fails After Using Setup ToolkitQ167950   DAO Internet Component Download Fails to InstallQ167951   AUTMGR32.EXE Fails After Component DownloadQ168153   DBGrid Bound to RDC Displays a Single Row After MoveLastQ168155   Crash When Resizing Column of Split DBGridQ168156   DBGrid Bound to RDC Displays Small ResultSets IncorrectlyQ168157   Problems Binding Multiple Controls to RDC 2.0Q168158   Can't Close Resultset if DBGrid Bound to RDCQ168159   DBCombo Updates Incorrectly When Using RDC Bound ListSourceQ168160   Error on Update After AddNew With RDC and Bound ControlsQ168161   Distributed Transaction Fails On Subsequent RunsQ168162   RDO Move 0 Fails to Refresh RecordQ168163   Memory Leak When Calling UserConnection Query EventQ169302   Get_Item() Does Not Return Error When Property Not FoundQ169303   Get_Item() Doesn't Find Property Defined on Ancestor IfaceQ169304   Errors Occur When Getting Property of VB Project: CrashesQ169305   Repository Error after Halting Execution in Break-mode EditQ169306   ReComputeRepository GPFs if Passed Non-existent DB NameQ169307   RepUtil:CompactJetRepository Doesn't Work with DSN NameQ169308   CompactJetRepository Only Recognizes Lowercase Jet db NamesQ169309   Adding ActiveX Designer/Userconnection Results in ShutdownQ169331   RecomputeRepos: Won't Work with Database Created by UML.DLLQ169332   Changing Obj Name Before Saving Results in Repository ErrorQ169333   Engine: Collection Not Updated After Removing an ItemQ169334   IRepos::Get_Name() Returns Error if Called on a PropertyQ169335   CDatabase::InsRelshipRow Does Not Release Collection ObjQ169336   Engine Item Method Takes Parameter Type of IntIDQ169337   Unable To Remove a Relationship from Collection with OBJIDQ169339   RepUtil.DLL Doesn't Contain Version or Copyright InformationService Pack 2 fixes:Q166908   ScaleMode for Printer Object Can't Create Custom ScaleQ167107   Missing Controls on the SSTAB Control TabsQ167165   Too Many Controls on a Form May Crash Visual Basic IDEQ167213   Invalid Page Fault When Shutting Down Visual Basic 5.0Q167346   GPF Occurs When Starting Visual Basic 5.0Q167706   Internet Transfer Control 5.0 "POST" Request Doesn't WorkQ167735   Setting Printer to Item in the Printers Collection FailsQ168290   GPF When Setting Font of Multi-selected ControlsQ168744   Printer May Lose Font AttributesQ168766   Internet Transfer Control Fails on Case-Sensitive ServerQ168792   Statusbar Time Panel May Not Update ProperlyQ171470   Resize Event Not Fired When UserControl Copied and PastedQ171471   VB-Created Controls Fail to Print with UserControl_PaintQ171472   Toggling PortOpen w/MSCOMM32.OCX Leaks Memory on Win95Q171473   MCI32.OCX Does Not Save Recorded .WAV FilesQ171474   Path Problems Using Project on Network ServerQ171475   RichTextBox Cleared When BorderStyle Changes at Run-TimeQ171476   Masked Edit Control Right-Aligned with NT 4.0 SP3Q171477   Format Menu Options Can Crash Visual Basic 5.0Q171478   Cannot Set Width/Height of UserControl in Resize EventQ171479   Mod 0 Causes an IPF or Access ViolationQ171480   Setting SelAlignment Property Does Not Affect RichTextBoxQ171481   Cannot Set the Enabled Property of an UpDown ControlQ171482   Crash When Enum Name Referred to IncorrectlyQ171483   Crash When Rebuilding EXE Containing UserControlQ171484   Code Module Window Displayed Transparently in SDIQ171485   Visual Basic 5.0 Title Bar Paints IncorrectlyQ171486   Crash Sometimes Occurs with Cursor over ToolboxQ171487   Crash When Assigning Uninitialized Object to TagQ171488   Val Function Recognizes System Decimal SymbolQ171489   Use of Implements and Public Constants Crashes CompilerQ171490   Crash After Toggling Folders in ActiveX EXE ProjectQ171491   Mouse Button Value Is Always 4 in MouseUp Event of SSTabQ171492   ActiveX Control Incorrectly Reports ScaleWidth/ScaleHeightQ171493   Viewing Property Pages and Exiting Causes Memory LeakQ171494   MouseUp Event Not Triggered in DblClick w/Comctl32Q171495   Get Statement Not Working Correctly with Large UDTQ171496   Bad Filename or Number with Get of UDTQ171497   ListView in PictureBox on Tabbed Dialog DisappearsQ171498   Screen Turns Black When CompilingQ171499   IDE Doesn't Show Topics of OCX Help Files CorrectlyQ171500   ATL Controls Without IPropertyNotifySink Cause IPF in VB5Q171501   User Control Moves When Width/Height Is Set in ContainerQ171502   Crash with Watch on UserControl When Stop is EncounteredQ171504   Problems Setting PropertyPage Caption PropertyQ171505   VB5 IDE Disappears or IPFs When "End" Button Is PressedQ171506   OLE Drag/Drop of ListView Control FailsQ171507   VB GPFs When Selecting Align/Lefts from the Format MenuQ171508   Add-ins May Cause Menu Corruption When Exiting Visual BasicQ171509   Access Violation on NT4.0 on Multi-line TextboxQ171510   Setting Font Property Causes Error 438 with RichTextBoxQ171511   Controls in Frame/PictureBox Do Not Repaint in Design ModeQ171512   UserControls on Property Pages Do Not Trigger Focus EventsQ171513   Cannot Drag a Nested UserControl with Automatic DragModeQ171514   Visual Basic 5.0 Crashes When Shutting Down FormsQ171515   Crash on Customization of Design Environment MenusQ171516   ActiveX Document DLL Causes GPF When Unloading Modal FormQ171517   Animation Control Prints Incorrectly at Design-TimeQ171518   Controls May Not Print When Printing Form at Design TimeQ171519   Removing Function Causes Binary Compatibility ErrorQ171520   Unable to Set Binary Compatibility with Class ModuleQ171521   Non-Creatable Class Causes Loss of Binary CompatibilityQ171522   Enums in Public Procedures Cause Binary Compatibility ErrorQ171523   Reference to Missing Member in Enum Definition Causes CrashQ171524   Ambiguous Names Generate Incorrect Error MessageQ171525   ListView Causes IPF When Accessing ColumnHeaders PropertyQ171526   Setting Enabled=False for TreeView Causes Paint ProblemsQ171527   Causing a ListView Control to Paint Causes an IPFQ171528   Using "Unload Me" in a Listbox Causes CrashQ171529   Can't Open a Project Group from the Root DirectoryQ171530   Crash on Data Tip After Enum Name ChangedQ171531   IPF When Changing Project Name With Binary CompatibilityQ171532   Crash Stepping Thru Code After Using Locals/Watch WindowQ171533   ActiveX EXE Crashes VB5 When Set to Binary CompatibilityQ171575   RISC: CByte Doesn't Fail on Negative Values on Native ExeQ171576   RISC: AddressOf Doesn't Behave Properly in IDE/PCode ExeQ171577   Using Set for ListItem's SubItem Results in GPFQ171795   RDC Error Calling UpdateRow After Resultset.AddNewQ171796   Problems When Running Asynchronous Queries with RDO 2.0Q171797   VB5 DBCombo May Display Wrong Column for RDC 1.0Q171798   DBCombo Click Event Fires During Form LoadQ171799   RDO May Incorrectly Handle Locking Conflicts in TransactionQ171800   Unexpected Shutdown When Using Bound ControlsQ171801   Bound Controls Built in VB5 Do Not Work in VB4 IDEQ171802   Problems Updating Using DBCombo When ListField = DataFieldQ171803   Problems Retrieving VB 5.0 Projects from Visual SourceSafeQ171804   Change Event Not Fired When Selecting an Item in DBComboQ171805   Problems Binding Controls To Nonexistent Data ControlQ171806   Memory Leak When RDC Bound to OLE Container ControlQ171807   Selected Tab Changes After Removing Tab in TabstripQ171808   MDI Child Form Does Not Become ActiveQ171809   Memory Leak When Setting the ForeColor of a VB5 ObjectQ171810   Invoking the Visual Component Manager asserts in ExutilQ171811   Cannot see relationship collection on an interface with TabQ171812   Run-Time Error When DataObject Passed As ObjectQ171813   IPF in MSO97RT.DLL When Starting Visual BasicQ171814   System Menu Appears When MouseDown Event Invokes a DragQ171815   Printer.TextWidth Returning Inconsistent Results in IDEQ171816   IPF Opening or Saving Form with Tab ContQ171817   UserControl Cannot Read ContainedControls in Visual FoxProQ171818   IDE Crashes When Repeatedly Placing a Control on a FormQ171819   Invalid Enum Value Causes Incompatible Binary CompatibleQ171820   ListView ListItems Don't Refresh When ColumnHeaders ClearedQ171821   Memory Leak When Repeatedly Changing Toolbar Button WidthQ171822   Adding a Routine to UserControl in Break Mode Causes CrashQ171823   Application Error When Using Implements on Hyperlink ObjectQ171824   Crash in INET Control Downloading Page Multiple TimesQ171825   Tabbing Problems Using ActiveX Document in a FrameQ171826   Tabbing Problems with Controls Contained with ControlsQ171827   Printing userdrawn usercontrol in IE Doesn't WorkQ171828   Using OpenURL Doesn't Download Complete FilesQ171829   GetChunk Freezes Unless Other Events HappeningQ171830   ActiveX Document Menu Changing PlacesQ171831   IObjectSafety Implemented in Toolbar and CmDialog ControlsQ171832   Statement Builder Can Cause the Object Browser to CrashQ171833   Statement Builder Crashes Referencing GlobalMultiUse ServerQ171834   Crash When UserControl Accesses Members of ParentControlsQ171835   Crash When Viewing Data Tips on ParamArrayQ171836   Crash When Viewing API Properties in Object BrowserQ171837   Run-time Error 6 "Overflow When Compiled to Native Code"Q171838   Crash Compiling Native Code for Assignment of Variant ArrayQ171839   Crash When Compiling a Call to a UserControl FunctionQ171840   Corrupt Project Error Opening One Project After AnotherQ171841   Dragging Multiple Controls on a Form May Cause CrashQ171842   GetSetting Function Is Leaking HandlesQ171843   Winsock Control Leaks Memory When UnloadedVisual C++ KB ArticlesService Pack 1 addresses the following issues.Q165792   MSDEV.EXE Application Error When Building an ApplicationQ166282   C2440 Caused by Template Function with Const PointerQ166285   MSDEV Crashes When Converting VC++ 4.0 ProjectsQ166718   C1001 from Conditional Operator in InitializerQ167423   CRecordset Members Not in "Add Member Variable" Dialog BoxQ167845   Class Wizard Deletes Source FilesQ167994   Cvpack INTERNAL ERROR When Linking Large ProjectsQ168007   Remote Debugging Very Slow in Visual C++ Version 5.0The fixes for the Active Template Library (ATL) shown below address themost commonly reported issues: MBCS compatibility, container compatibilityissues, and internal coding errors in ATL.Q167340   ATL Control Causes Access Violation in Visual Basic 5.0Q167526   ATL Control May Cause An Access ViolationQ167949   OnWindowMessage Returns BOOL for HRESULTThe compiler fixes shown below address the most commonly reported COMissues.  These issues include: support for VB-created controls, internalcoding issues in the COM headers, and problems related to smart pointersand reference counting.Additionally, there are fixes for templates that contain improperpropagation of the "const" qualifier, and fixes for a problem of forcinginstantiation of all template member functions regardless of whether theywere actually used.There were also reported problems with either floating point optimizations,the global optimizer (/Og) or both.  All these reported issues have beenaddressed in this Service Pack.Q151491   copy() Member of bstrt in COMUTL.H Doesn't CopyQ151499   Compiler Performs Illegal Sign Conversion OptimizationQ151500   /Og Causes vfptr Initialization ProblemsQ166721   C2784 On < Operator When Instantiating an ATL ContainerQ167967   /Og Increments the Index of a Loop Too Soon.Q167995   Calling a Function Returning double May Not pop FPU StackQ167996   /Og Causes Invalid Double Result Returned from FunctionQ168003   Function Prototypes in comutil.h Missing Calling ConventionQ168008   C2166: Incorrect Type Deduction for Template ParameterQ168009    Smartptr Property in Interface Causes C2512 ErrorQ168010   /Od May Generate Destructor for Unconstructed Temp ObjectQ168011   C1001, file 'fppeeps.c', line 394, Caused By /OgQ168012   Incorrect Code Generated When Using Floating-Point and /OgQ168028   C2955: Caused By the "using" DeclarationQ168029   Global Optimizations (/Og) May Cause the Compiler to HangQ168079   _com_ptr_t::operator=(const _variant_t&) AddRefs TwiceQ168111   #import Does Not Compensate for Gaps in vtableListed below is a Linker fix that corrects a reported problem that ICF(Identical COMDAT Folding) was causing severe build-time losses. The fixalso removes limits being imposed on the size of an executable and raisesthe maximum size of the .ilk file used by the linker to 64 MB.Q151501   Linking Large Projects Can Be Very SlowThe fixes for the Microsoft Foundation Classes (MFC) listed below deal withthe most commonly reported issues that prevent binary compatibility withMFC 4.2 (shipped with Visual C++ 4.2). These issues include unintendeddependencies on the latest comctl32.dll, the 3.0 version of odbc32.dll,threading issues, and internal coding errors in MFC.Q164813   Web Browser Control Hangs in CFormViewQ167423   CRecordset Members Not in "Add Member Variable" Dialog BoxQ167650   Problems with ToolTips on Windows 95Q167692   Assertion Line 257 in File DlgProp.cppQ167693   MFC Application Hangs on Multiprocessor MachineQ167731   Access Violation When Connecting in MFC ODBC ApplicationQ168004   "Unable to Initialize DAO/Jet db Engine" ErrorQ169484   CString::MakeUpper and MakeLower Don't Work with Some CharService Pack 2 fixes some debugger issues. The debugger now evaluatescompiler-generated strings longer than 128 characters (this usually takesplace when you are debugging templates, such as STL) without encounteringan access violation. Also, the debugger now starts smoothly inconfigurations that have Visual Test and Visual C++ integrated.Q171848   Source Control Info Not Preserved During Project ConversionQ171849   Debugger Hangs When Very Long STL Symbol in Watch WindowVisual Database Tools KB ArticlesQ168295   Updating Single Row Replaces Data in All Rows of a CursorVisual FoxPro KB ArticlesService Pack 2 fixes the access violation error problem when running a formwith a grid repeatedly under Windows NT 4.0. OLE automation with Word 97issues have been addressed. Some of the report printing and previewproblems under Windows NT also have been fixed.Q156322   RETURN TO Procedurename Command Doesn't Work in FormsQ156788   Report Print Preview Illegible Under Windows NTQ168277   Access Violation Running Form With Grid Repeatedly on NT 4Q168523   Report Fails When Printing Under Windows NT 4.0Q169565   Type Mismatch Using OLE Automation to Word 97Service Pack 2 fixes the Anomaly Tracking System (ATS) so that it does notdisplay the 'Option under construction'  message when action items areselected.Q168193   'Option under construction' Message Appears in ATSVisual InterDev KB ArticlesService Pack 1 fixes various wizard problems. The Service Pack also fixes abug that destroys data in situations when FrontPage editor, which comeswith Visual InterDev, is used.Q165834   Can't Set Permissions Back to Root Web PermissionsQ167267   New Devisws.pkg for 0-Byte File Save ProblemQ167836   DataForm Wizard Not Sizing Column Width Properly For DBCSQ167846   Reserved Error When Running DataForm Wizard Against AccessQ168269   MSWC BrowserType Control Does Not Recognize IE 3.02Q168270   Update Error When Updating Sybase Table From ASPQ168271   Sybase Cursor Can't Scroll Back in DF Wizard Created FormQ168272   GPF When Refreshing a Project Containing Sybase ConnectionQ168273   Invalid Operation When Deleting the End Sybase RecordQ168274   GPF When Selecting .ALX Files in Template WizardQ168275   Corrupted Dialog Titles in Japanese VersionQ168296   GPF When Expanding Links in Japanese Version of VIQ168297   Data Connection Icons Not Displayed for global.asaVisual J++ KB ArticlesService Pack 1 contains fixes that will enable customers to debug Javaapplets running on Microsoft Internet Explorer 4.0 (but not on MicrosoftInternet Explorer 4.0 Preview Release 1). If you are running MicrosoftInternet Explorer 4.0 Preview Release 1, you should upgrade to MicrosoftInternet Explorer 4.0 Preview Release 2, which is available now on the website  For multi-processor machines,Service Pack 1 fixes a scenario that resulted in a fault. It also fixes anisolated case in which ClassView did not display any information.Q167719   JavaTLB gives an Internal Compiler Error With VBCCE ControlQ167720   Saving Java File on Multi-Processor Machine Crashes MSDEVQ167828   Cannot Access the ClassView Information File ErrorQ167998   Cannot Debug Visual J++ Programs on IE 4.0 Pre-ReleaseSee Visual C++ KB Articles for Service Pack 2 fixes that may affect VisualJ++ users.Visual SourceSafe KB ArticlesService Pack 1 contains five fixes for Visual SourceSafe: the deployment offiles placed in the parent directory to a UNIX Server; movement of randomcharacters to the end of the file after SourceSafe editor is used;incomplete check in of files in Visual Basic or Visual C++ when keywordexpansion is enabled; corruption of Rights.dat after adding rights byproject; and slowdown of analyze and appearance of hanging on largedatabases.Q165776   Admin Cannot See Files With Project Security EnabledQ166469   Multiple Check In Fails with Keyword ExpansionQ167273   VSS Editor/Viewer Removing or Replacing CharactersQ167274   Analyze May Hang or Crash When Running on Large DatabasesQ167737   Deploy to a Unix Server Via FTP FailsService Pack 2 contains Visual SourceSafe fixes for a memory leak in theVisual Studio integration, and an access violation in Analyze, a developertools integration issue where files like Status.dat are needlessly keptopen.Q171534   Source Code Control Integration Holds .dat Files OpenQ171535   ANALYZE Crashes When No Log Entries Found in Log FileNOTE: the original and incorrect title to Q171535 was: "ANALYZE ApplicationError When Directory Not Found".Welcome to Visual Basic 5.0 Service Pack 2------------------------------------------Visual Basic 5.0 Service Pack 2 is an update to Visual Basic Version 5.0Professional and Enterprise editions. It enables apartment-model threadingfor Visual Basic projects that contain user interface elements, such asforms and controls.DocumentationThe apartment-model threading enhancement in Visual Basic 5.0 Service Pack2 is explained in vb5sp2.htm (vb5sp2.wri on some systems). This filecontains information supplementing the Books Online documentation youreceived as part of your licensed copy of Visual Basic.Bug FixesThe Microsoft Visual Basic team closely monitored feedback from programmersafter Visual Basic 5.0 shipped. Every effort was made to reproduce and fixthe most serious and commonly reported problems. Visual Basic 5.0 ServicePack 2 fixes problems with the development environment, the Printer object,the Internet Transfer control, and many of the other controls and librariesthat ship with Visual Basic 5.0. The Visual Basic team made every effort toensure backward compatibility with shared components.Development environment: Visual Basic 5.0 Service Pack 2 resolves severalstability problems in the development environment, including crashes thatsometimes occurred when moving the mouse cursor over the toolbox, whensetting the Font properties of multiple controls, and when using the Formatmenu options to align controls.Printer object: Setting the Printer object to an item in the Printerscollection will now switch the default printer. You can now set a user-defined scale mode for the Printer object by changing the ScaleWidth andScaleHeight properties. Font attributes are no longer lost when calling theNewPage method.Internet Transfer control: POST now works. Problems with missing or garbleddata have been fixed. The control no longer converts file names to uppercase when sending out a request, thus eliminating reported problemsaccessing case-sensitive servers.For a complete list of bug fixes included in Visual Basic 5.0 Service Pack2, search the Microsoft Knowledge Base at for articles containing the keywordVB5FixlistSP2.Dependency ListVisual Basic 5.0 Service Pack 2 includes a new master dependency file(vb5dep.ini), which is installed in the Setupkit directory. The existingdependency file is renamed ~vb5dep.sp2.Removing Visual Basic 5.0 Service Pack 2 and Restoring Visual Basic 5.0Visual Basic 5.0 Service Pack 2 modifies Visual Basic 5.0 by replacing somefiles and updating system information. To remove SP2, you must open theControl Panel and use the Add/Remove Software tool to remove Visual Basic5.0 from your system. Manually delete any remaining SP2 files beforereinstalling Visual Basic 5.0. (For a complete list of files included withSP2, see the SP2 documentation file - vb5sp2.htm or vb5sp2.wri.)				
For additional information, please see the following articles in theMicrosoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why

170367 HOWTO: Determine VS97 Service Pack Updates in a Product

171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2

175869 INFO: Troubleshooting the Visual Studio Service Pack 2 Download
The equivalent of this article for the Visual Studio 97 Service Pack 1 is:
170366 INFO: Visual Studio 97 Service Pack 1 Readme
kbVBp500 kbVBp kbWinCE100 wince kbVS97sp1 kbVS97sp2 kbreadme kbVS97SP3

Article ID: 172610 - Last Review: 12/04/2015 17:38:26 - Revision: 3.0

Microsoft Visual C++ 5.0 Enterprise Edition, Microsoft Visual C++ 5.0 Professional Edition, Microsoft Visual Basic 5.0 Learning Edition, Microsoft Visual Basic 5.0 Professional Edition, Microsoft Visual FoxPro 5.0 Standard Edition, Microsoft Visual FoxPro 5.0a, Microsoft Visual J++ 1.1 Standard Edition, Microsoft Visual SourceSafe 5.0 Standard Edition, Microsoft Visual InterDev 1.0 Standard Edition, Microsoft Visual Studio 97 Enterprise Edition, Microsoft Visual Studio 97 Professional Edition

  • kbnosurvey kbarchive kbreadme kbinfo kbvs97sp1fix kbvs97sp2fix KB172610