KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q33622: COMMON SHARED Problem when Period in Variable after CHAIN

Article: Q33622
Product(s): See article
Version(s): 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | buglist4.00b buglist4.50 | mspl13_basic
Last Modified: 12-DEC-1989

When CHAINed inside the QuickBASIC Version 4.00b or Version 4.50
editor, the following programs fail to pass the COMMON SHARED variable
m$. There are no error messages at compile time or run time. The
CHAINed program uses a period in an array name that appears to
conflict with a separate user-defined type. Neither the array nor the
user-defined type variable is passed in COMMON. The programs run
correctly in QuickBASIC Version 4.00 or when run from an .EXE program
compiled in Version 4.00b or Version 4.50.

Microsoft has confirmed this to be a problem in QuickBASIC Versions
4.00b and 4.50. This problem was corrected in the QBX.EXE environment
of the Microsoft BASIC PDS Version 7.00 (fixlist7.00).

The following is a code example:

   'The CHAINing program, PROG1.BAS:
   COMMON SHARED m$
   m$ = "Nice to see you.  Sometimes I don't print, but I should!"
   CHAIN "prog2"

   'The CHAINed-to program, PROG2.BAS:
   COMMON SHARED m$
   TYPE t
     a AS INTEGER
   END TYPE
   DIM c.n(5)    'If the period is taken out, it works correctly.
   DIM d AS t    'If this line is taken out, or if d is DIMmed to
                 'something else, it works correctly.
   PRINT m$

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 1986-2002.