



                        M E S S A G E    B O X    M A K E R


              by
              Gordon Burnham
              631 Iroquois Avenue
              Louisville, KY 40214-1226
                    USA
              Tel (502) 363-5136


        MESSAGE BOX MAKER Copyright (c) Gordon Burnham 1994.  All rights
        reserved.  MESSAGE BOX MAKER is a proprietary computer software
        product provided by its copyright holder, Gordon Burnham (631
        Iroquois Avenue, Louisville, KY); both the software and its
        documentation are copyrighted, and you may not copy or use either
        except as expressly provided in writing by Gordon Burnham.
        
        MESSAGE BOX MAKER for Windows, Version 1.6, is offered on a
        shareware (try before you buy) basis.  If you find this program
        useful and/or use it after a 30-day trial period, you are
        expected to register it with the author.  Registration is $15

        MESSAGE BOX MAKER is written in Visual Basic and therefore will
        require the 'VBRUN300.DLL' which comes with Visual Basic.  If you
        have an older version, you can get this one from the MSBASIC
        forum on Compuserve.  If you have problems with the VBX, try 
        putting it in your 'windows\system' directory.
        
        MESSAGE BOX MAKER is a utility designed for Visual Basic
        programmers.  It a very handy mechanism for creating "Message
        Boxes".  It allows you to build a message box, test it, modify
        and test again until you get it right.  You can then paste the
        code into a function or subroutine.
        
        I have found it very useful for creating message boxes for User
        approval.  It makes it very easy to create, 'screen print' and
        place into a Word for Windows document.  Several variations can
        be done this way very quickly to determine the best for a certain
        situation.
        
        A number of programmers have told me that what they like most 
        about MESSAGE BOX MAKER is that you don't have to try to remember
        or go look up the codes for the buttons, icons, setting the 
        default button, return values from the button clicked or how to
        make the message box application modal or system modal.
        
        Essentially, you create the message box, test it, when it's the
        way you want it, click the 'Copy to Clipboard' button, go to the
        place in your code where you want the message box and perform a
        paste.  Voila!  The complete code for the message box is there, 
        requiring only that you enter the code for the appropriate response
        to the buttons chosen for this particular message box.


        NOTES ABOUT USE:

        This readme file is the only documentation for MESSAGE BOX MAKER
        since, for even novice Visual Basic programmers, it fairly
        obvious how to use it.  The following information is provided so
        that you don't have to experiment to find out how they work, but
        you'll probably want to do that anyway!

        When building the message box you have several options for how
        you want the code to be generated.
        
        1.  Use Visual Basic Constants - checking this will cause the 
            code to be generated with VB constants.  You will need to
            make sure that 'Contant.Txt' (from Microsoft) is included
            in a code module.  If unchecked, then acutal numbers will
            be used.
            
        2.  No variables - checking this will cause the message box 'text'
            and message box title to appear as string literals in the
            "MsgBox" call.  This will also check & disable the checkbox
            labeled "No Variable Declarations" for obvious reasons.  If 
            unchecked, the variables 'MBMsg$ & MBTitle$' will be used to
            hold the 'text' & 'title' strings.
            
        3.  No variable declarations - If unchecked, the line "Dim MBMsg$,
            MBTitle$" will be included in the code.  If you already have 
            used variable declarations within the Function or Subroutine,
            you will get a VB error message telling you the declaration
            is a "duplicate declaration", so you may want to check this
            if this is the case.
            
        Message boxes can be generated using different combinations of
        these items to suit your particular preference.

        

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
END OF README.TXT
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
