Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : DB4ANOM.ZIP
Filename : ANOMALY7.TXT

 
Output of file : ANOMALY7.TXT contained in archive : DB4ANOM.ZIP
ANOMALIES UPLOADED ON 03-17-89


ANOMALY7.TXT


In keeping with our commitment to provide you, the user, with
support that will maximize your productivity with the dBASE IV
product, we are continuing our tradition of publishing timely,
detailed anomaly and work-around reports.

The following listing addresses one known anomaly when using
dBASE IV. Use of these techniques will aid you in avoiding
anomalies that have been reported to our Software Support
Center. This report will be supplemented as new information is
received. There is also one Usage Tip that may be used in order
to avoid further problems or misunderstandings when using the
dBASE IV product.



*************************************************************************************


ANOMALY


Blank lines are not suppressed in labels

When a line on a label form contains blank data (as in a company
name field) dBASE IV's Label.GEN inconsistently suppresses blank
lines. This is incompatible with dBASE III PLUS which suppressed
any blank lines. This problem occurs when Columns of labels is
defined as 2 or more. In order for any line in a label to be
suppressed, every line has to be a blankable line. The criteria
for a blankable line is any of the following:

- Any line containing a single character field.

- A number with the 'Z' function in the template.

- Any line containing one or more fields that has no
additional character or literal.

EXAMPLE:

If the line is comprised of:

City, State

the literal comma prevents the line from becoming a
blankable line. If a line of a label needs to have a literal
comma, you may create a calculated field comprised of:

TRIM(City)+", "+State



WORKAROUND:

Download the updated file Label.GEN from the dBASE IV
Library and copy it over the Label.GEN in your dBASE IV
directory. This new .GEN file will automatically suppress blank
lines.

This new Label.GEN also incorporates the fixes that were included
in the Label.GEN that was uploaded on 1-20-89, and 1-27-89.

================================================================================

USAGE-TIP



Use on Environmental Variable SET DTL_xxxx


Certain objects expect compiled templates which have specific
names. With the use of a DOS environmental variable, the template
name can be other than the default template filename.

OBJECT TEMPLATE NAME DOS Environment Variable

Forms Form.GEN SET DTL_FORM =
Reports Report.GEN SET DTL_REPORT =
Labels Label.GEN SET DTL_LABEL =
Quick Applcation Quickapp.GN NONE


EXAMPLE:

In order to use a different version of the Label.GEN file, one
might copy the file to the same directory in which dBASE IV is
installed, but under a new name (e.g. Label.222). From DOS issue
the command:

SET DTL_LABEL=Label.222

Upon generating any new label form within dBASE IV, the new .LBL
file generated will use the Label.222 file specified via the SET
DTL_LABEL environmental variable.

For more information, refer to page 3-1 of the Template Language
manual which is included with the Developer's Edition of dBASE
IV.

================================================================================


  3 Responses to “Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : DB4ANOM.ZIP
Filename : ANOMALY7.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/