!|*|1K|w0000000012|S0107|B0000HR9P|Y00000100
!|1B00000000LC02000009080100000001000000|1U3102EM1A0000
!|1B00000000LC02000008090100000001000000|1U3808EF140000|W0|c04|=00000000
!|L181YGD1Y|c0C|L181ZGD1Z|c0E|L1820GD20|c0A|L1721GD21|c02|L1822GD22|c0B
!|L1723GC23|c03|L1824GC24|c09|L1825GD25|c01|L1826GD26|c05|L1827GD27|c0E
!|Y07000100|@6T0BHelpfull Hints|c00|Y02000400
!|@122EBefore using WCRIPBRO, make sure you read the README.DOC file and have \
a general understanding
!|@0P2Rof WCRIPBRO, and its command structure.  Next, as with most things, rem\
ember that planning is almost
!|@1A34always the KEY to SUCCESS.  Plan out your structure in advance, and ass\
ign filenames for the
!|@183Hvarious pages you wish to display, so that as you make each screen you \
will know what other 
!|@383Uscreens (pages) you wish to reference with mouse regions or buttons.
!|@8N47 
!|@124KDecide on a general display layout and format that you will use through\
out your pages.  Keeping
!|@154Xpages uniform in presentation and operation is not only more profession\
al, but easier for the 
!|@1Y5Auser to learn and operate.  Also, with a standard layout, you can keep \
a boilerplate
!|@385Nbackground to call up instead of starting each screen from 'scratch'.
!|@8N60 
!|@196DIf you have a problem, read the manual first - and compare what you are\
 trying to do against|@506Qthe examples given for each type of command.  |c02
!|L187GGD7G|c0B|L177HGC7H|c03|L187IGC7I|c09|L187JGD7J|c01|L187KGD7K|c05
!|L187LGD7L|S0101|B39897L98|c0B|R3B8B7I96|c0E|Y07000100|@488FTravNet\!
!|Y02000400|1B0000020QOG020E000908010E000E01000000
!|1U9X8DBV942500<>Main<>WCRB0.RIP^M|1UC38DE1942900<>QUIT<><0>^M
!|1U7Q8D9O942800<>Prev<><P>^M|c08
!|@2Y9CCopyright (c) 1994, 1995 by TravNet\! International - All Rights Reserv\
ed|1M00H307H3071000000<XN>HELP^M|1M00HA01HA011000000<XN>HELPFULL HINTS^M
!|1M00HI0BHI0B1000000<XK>HELP^M|1M00GZ0PGZ0P1000000<XK>HINT^M
!|1M00H20HH20H1000000<XK>WCRIPBRO^M
!|#|#|#
