DOCUMENT:Q190775 07-AUG-1998 [vbwin] TITLE :INFO: Installation Requirements for Visual Basic 6.0 PRODUCT :Microsoft Visual Basic for Windows PROD/VER: OPER/SYS:WINDOWS KEYWORDS: ====================================================================== --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 6.0 --------------------------------------------------------------------- SUMMARY ======= This Article describes the minimum installation requirements needed in order to run each edition of Microsoft Visual Basic 6.0. MORE INFORMATION ================ MINIMUM SYSTEM REQUIREMENTS Learning Edition ----------------- - Multimedia PC with a 486DX/66-MHz or higher processor (Pentium or higher processor recommended) - Microsoft Windows 95 or later operating system or Windows NT operating system version 4.0 with Service Pack 3 or later (Service Pack 3 included) - 16 MB of RAM for Windows 95; 24 MB for Windows NT 4.0 - Microsoft Internet Explorer 4.01 Service Pack 1 (included) - Hard disk space: - Typical installation: 52 MB - Maximum installation: 65 MB Additional hard disk space may be required for the following products: - Internet Explorer: 43 MB typical, 59 MB maximum - Microsoft Developer Network (MSDN): 57 MB typical, 493 MB maximum - Learn Visual Basic Now: 16 MB including labs - CD-ROM drive - VGA or higher-resolution monitor; Super VGA recommended - Microsoft Mouse or compatible pointing device Professional Edition -------------------- - PC with a 486DX/66-MHz or higher processor (Pentium or higher processor recommended) - Microsoft Windows 95 or later operating system or Windows NT operating system version 4.0 with Service Pack 3 or later (Service Pack 3 included) - 16 MB of RAM for Windows 95 (32 MB recommended); 24 MB for Windows NT 4.0 (32 MB recommended) - Microsoft Internet Explorer 4.01 Service Pack 1 (included) - Hard disk space: - Typical installation: 76 MB - Maximum installation: 94 MB Additional hard disk space may be required for the following products: - Internet Explorer: 43 MB typical, 59 MB maximum - MSDN: 57 MB typical, 493 MB maximum - Windows NT Option Pack: 20 MB for Windows 95; 200 MB for Windows NT 4.0 - CD-ROM drive - VGA or higher-resolution monitor; Super VGA recommended - Microsoft Mouse or compatible pointing device Enterprise Edition ------------------ - PC with Pentium-class processor; Pentium 90 or higher processor recommended - Microsoft Windows 95 or later operating system or Windows NT operating system version 4.0 with Service Pack 3 or later (Service Pack 3 included) - 24 MB of RAM for Windows 95 (32 MB recommended); 24 MB for Windows NT 4.0 (32 MB recommended) - Microsoft Internet Explorer 4.01 Service Pack 1 (included) - Hard disk space: - Typical installation: 116 MB - Maximum installation: 135 MB Additional hard disk space may be required for the following products: - Internet Explorer: 43 MB typical, 59 MB maximum - MSDN: 57 MB typical, 493 MB maximum - Windows NT Option Pack: 20 MB for Windows 95; 200 MB for Windows NT 4.0 - Microsoft SQL Server 6.5 run on Windows NT 4.0 only and require the following additional hard disk space: SQL Server: 80 MB typical, 95MB maximum - CD-ROM drive - VGA or higher-resolution monitor; Super VGA recommended - Microsoft Mouse or compatible pointing device Additional query words: kbdss kbDSupport kbVBp kbSetup kbVBp600 <<>> 190727 <<>> 1 <<>> HOWTO: Control Your Updates in ADO Via "Update Criteria" <<<LONGTITLE>>> HOWTO: Control Your Updates in ADO Via "Update Criteria" <<<PRODUCT>>> vbwin <<<PRIORITY>>> 2 <<<SECURITY>>> PUBLIC <<<AUTHOR>>> davidsc <<<EDITOR>>> pjriker <<<EDITSTATUS>>> Released <<<TECH>>> matthofa <<<TECHSTATUS>>> Approved <<<EXPIREDATE>>> Dec 31 1999 12:00AM <<<MESSAGE>>> <<<KEYWORD>>> <<<INTERNALADMIN>>> <<<QUESTION>>> <<<PRODVERNUM>>> <<<COMPONENT>>> <<<TECHNOLOGY>>> <<<LINKS>>> <<<RAIDINFO>>> <<<INCIDENT>>> <<<SWEEPDATE>>> <<<SWEEPSTATUS>>> <<<SOLUTIONTYPE>>> <<<ISSUETYPE>>> kbhowto <<<PLATFORM>>> WINDOWS <<<HARDWARE>>> <<<BOILERPLATE>>> <<<PRODUCEDVIEW>>> <<<TEXT>>> --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Professional and Enterprise Editions for Windows, versions 5.0, 6.0 - ActiveX Data Objects (ADO), version 2.0 --------------------------------------------------------------------- SUMMARY ======= The ADO Client Cursor Engine allows you to control how it builds the action queries that update the database according to the changes you make to the recordset object. This article is designed to help you understand how to control how ADO performs these updates. MORE INFORMATION ================ When you open a recordset against the Customers table in the Northwind database (NWind.MDB) and use a client side cursor, ADO retrieves enough information about the structure of the table in order to use an action query to update the table. An action query is a query that modifies a database and does not return data. For example, "UPDATE Customers SET CompanyName = 'Acme' WHERE CustomerID = 17" is an action query. ADO determines which field, or set of fields, the primary key is in and uses that information to make sure it can find the correct row in the database to update. If you are going to perform updates with the client cursor engine, make sure you have a primary key defined in your table. If you don't, you may accidentally update more rows than you intended. When you use a client side recordset, ADO exposes a property in the recordset's Properties collection called "Update Criteria." This property allows you to control the information in the WHERE clause in the action query that ADO builds to update the database. The default value for this property is 2 - adCriteriaUpdCols. By default, ADO will use the primary key and all fields being updated in the WHERE clause of the action query. For example: rsCustomers.CursorLocation = adUseClient rsCustomers.Open "SELECT * FROM Customers", cnNWind, _ adOpenStatic, adLockOptimistic, adCmdText rsCustomers.Fields("CompanyName").Value = "Acme" rsCustomers.Update will cause ADO to execute the following action query: UPDATE Customers SET CompanyName = 'Acme' WHERE CustomerID = 'ALFKI' AND CompanyName = 'Alfreds Futterkiste' The WHERE clause contains information about the primary key and the original value for the field to update. This ensures that if another user has modified the value of the CompanyName field to a value other than the value that ADO originally retrieved, ADO will not update that row and will raise an error instead. To change the value of this property, use code similar to the following rsCustomers.CursorLocation = adUseClient rsCustomers.Properties("Update Criteria").Value = adCriteriaAllCols rsCustomers.Open "SELECT * FROM Customers", cnNWind, _ adOpenStatic, adLockOptimistic, adCmdText rsCustomers.Fields("CompanyName").Value = "Acme" rsCustomers.Update This code will cause ADO to include every field in the WHERE clause. You would use this value for the "Update Criteria" property if you want to make sure that the update made by the current user will only succeed if no changes have been made to any fields in that row in the table. The available constants for this property are as follows: adCriteriaKey = 0 Uses only the primary key adCriteriaAllCols = 1 Uses all columns in the recordset adCriteriaUpdCols = 2 (Default) Uses only the columns in the recordset that have been modified adCriteriaTimeStamp = 3 Uses the timestamp column (if available) in the recordset NOTE: Specifying adCriteriaTimeStamp may actually use adCriteriaAllCols method to execute the Update if there is not a valid TimeStamp field in the table. Also, the timestamp field does not need to be in the recordset itself. (c) Microsoft Corporation 1998. All Rights Reserved. Contributions by David Sceppa, Microsoft Corporation Additional query words: kbdse kbDSupport kbVBp kbVBp500 kbVBp600 kbADO200 kbNoKeyWord ====================================================================== Platform : WINDOWS Issue type : kbinfo ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1998.