Corrections for Errors in the Visual Basic for MS-DOS Manuals

• Microsoft Visual Basic Standard and Professional Editions for MS-DOS, version 1.0

SUMMARY

This article gives corrections for errors in the following manuals:

• "Microsoft Visual Basic Programmer's Guide"



• "Microsoft Visual Basic Language Reference"



• "Microsoft Visual Basic Professional Features"

MORE INFORMATION

Corrections to "Microsoft Visual Basic Programmer's Guide"

REMLINE.MAK is not shipped with Visual Basic. SORTDEMO.MAK and TORUS.MAK are included in the Professional Edition only. The file for the SPIN custom control is SPINDEMO.*, not CUSTCTRL.*.

The First Sentence of the first Note should read, "By default, the control with the TabIndex Property set to 0 will get the focus after the Form_Load precedure executes." In other words, change "set to 1" to "set to 0."

Remove the references to HELP.BAS, HELPF.FRM, and HELPUTIL.FRM. These files are not included in the standard edition.

"ir1_Click" should be "Dir1_Click"

The entire paragraph should be deleted.

The following declaration at the top of the code is incorrect:

      FUNCTION DirDiver%(NewPath AS STRING, DirCount AS INTEGER, ... 

Replace the entire line with the following:

      FUNCTION DirDiver(NewPath$, DirCount%, BackUp$) AS INTEGER 

And replace the following line:

      Dir1.Path = NewPath 

with this corrected line:

      Dir1.Path = NewPath$ 

Replace the following line:

      If BackUp$ THEN Dir1.Path = BackUp$ 

with the following corrected code:

      If BackUp$ <> "" THEN
         dirList.path = BackUp$
      END IF 

should read "and 0K of XMS for the programming environment."

"Quoted string literals" should be located under Near Heap Data (Dgroup), not Far Data Heap.

The Alias keyword is available in Visual Basic for Windows, not Visual Basic for MS-DOS.

All of the following string routines are available in Visual Basic for MS-DOS and are completely compatible with the Microsoft Basic Professional Development System: StringAddress, StringAssign, StringLength, StringRelease.

The illustration does not match the code that accompanies it. The text boxes should be labels and they should display different data.

The code that loads the form should be:

      CASE "B"
         frmSTUDENT.SHOW 1 

The "Form or Code &Module (.FRM; .BAS)" option button should say, "Form &Module (.FRM)" because .BAS modules are translated with the project option, but should be done by hand.

Corrections to "Microsoft Visual Basic Reference"

Keywords are shown in normal, uppercase in tables. Not bold. Keywords and literals are bold in syntax.

At the top of the page, remove the sentence that begins "ListIndex is set to -1 (no item selected) ..."

The third sentence that introduces the example should read "Printed output on the form is retained when the form displays because AutoRedraw is True." It is important to set AutoRedraw to True if you want to display printed output during the Load event.

The ForeColor property does not apply to the command button or scroll bars.

BorderStyle is read-only at run time for the forms and text box controls. It is read/write at run time for labels and picture boxes.

BorderStyle 3 has Minimize and Maximize buttons.

Event procedure parameters (Source, X, Y, and Index) should not be bold. You may use any names for these parameters. The ones shown are provided automatically when you create an event procedure with the Edit Event Procedures dialog box. This applies to all event procedure syntax in the Reference.

The value of n% cannot be >255.

The formatting characters for fmt$ are omitted. See online Help for this information.

The syntax for the $INCLUDE metacommand is as follows:

   {' | REM}$INCLUDE: 'filespec' 

If prompt$ exceeds the length of a line, it automatically wraps to the next line.

At the bottom of the page, remove the sentence that begins "ListIndex is set to -1 (no item selected) ..."

You can't use the comma with the USING clause in any of these statements or methods.

There is no DropDown event for menu controls.

The last line of example text should read:

   x% = MSGBOX(Msg$) 

The statement "Example See DIM Statement example" should be deleted.

The Print statement documentation is included under the LPRINT statement.

At the top of the page, remove the sentence that begins "ListIndex is set to -1 (no item selected) ..."

AutoRedraw does not apply to the SCREEN object.

In the example, the following statement is incorrect:

      If AfterCall <= BeforeCall THEN PRINT "Memory not reallocated."

   Change <= to < to correct the problem:

      If AfterCall < BeforeCall ... 

The first paragraph indicates that using WRITE # to print to the screen causes an error if used with forms. It should state that this causes an error if forms are currently displayed.

The scan code for decimal 78 is the gray + key, not - key shown.

"QUICKLIB.OBJ" should read "VBDOSQLB.LIB"

Corrections to "Microsoft Visual Basic Professional Features"

The first DECLARE statement is incorrect:

      DECLARE SUB SetProperty ... 

It should read:

      DECLARE SUB GetProperty ... 

The place holder segementname is the base name of the Basic source file plus the string _CODE. For example, if a module is named NEW.BAS, the segmentname is NEW_CODE.

      DECLARE SUB ChangeArray(S$)
      CALL ChangeArray(A$(1)) 

It should read:

      DECLARE SUB ChangeArray(BYVAL offset%)
      DIM a$(1 TO 10)
      FOR i% = 1 TO 10
         a$(i%) = STRING$(i%, ASC("A") + i% - 1)
         PRINT a$(i%)
      NEXT
      CALL ChangeArray(VARPTR(a$(1)))
      FOR i% = 1 TO 10
         PRINT a$(i%)
      NEXT 

The second bullet should be deleted.

Step 3 says that VBDPROF creates VPROF.BAT. Actually, VBDPROF creates PROF.BAT. Therefore, you need to change VPROF in step 4 to PROF.

There is no TOOLS.PRE file included with Visual Basic for MS-DOS.

Additional query words: VBmsdos 1.00 docerr

Keywords :
Version : MS-DOS:1.0
Platform : MS-DOS
Issue type :