
Anomaly Report:  Genifer 3.0

---[1]--------------------------------------------------------------------

PROBLEM:  Genifer doesn't let you create a field in the Data Dictionary
whose name begins includes the character "X".

COMMENT:  This problem was corrected in Genifer 3.02.

FIX:  A new GEN.OVL can be downloaded from the Genifer Users Group BBS.
The file name is NEWOVL.ZIP.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[2]--------------------------------------------------------------------

PROBLEM:  When you AUTOINDEX, Genifer recognizes only the first three
common fields as links.

WORKAROUND:  After Autoindex is finished, just MODIFY that index and
include the additional field(s).  If all of the link fields don't fit,
you must change some of the field names to shorten the expression.  (You
should also re-evaluate your design to determine if all of those link
fields are really necessary.)

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[3]--------------------------------------------------------------------

PROBLEM:  When generating maintenance or inquiry programs, the loop
<< for all fields in window >> includes fields from subsequent windows.

COMMENT:  This loop is not employed in any Bytel templates, so the issue
is relevant only if you're creating custom templates.  This problem was
corrected in Genifer 3.02.

WORKAROUND:  The following code will accomplish exactly the same thing,
though the order of the fields may conceivably be different if you've
done something unusual with the field sequencing in the window.

   << for all zoom-databases in window >>
     << for all fields in database >>
     .
     .
     .
     << endfor >>
   << endfor >>

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[4]--------------------------------------------------------------------

PROBLEM:  In the layout editor, if you press [F2] to enter a field, press
[F2] again to pick a database name, and then press [Ctrl-rightarrow] or
[Ctrl-leftarrow], Genifer locks up and you must re-boot your system.

COMMENT:  This problem was corrected in Genifer 3.02.

WORKAROUND:  Don't use this particular sequence of key strokes.  (Even
if it didn't hang the program, it wouldn't accomplish anything.)

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[5]--------------------------------------------------------------------

PROBLEM:  When you add a new index in the Data Dictionary, press [F2] to
select a database name, then press [F2] again to select index fields,
the field pick list is sometimes for the wrong database.

COMMENT:  This problem was corrected in Genifer 3.02.

WORKAROUND:  This doesn't occur if you type in the database name instead
of picking it.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[6]--------------------------------------------------------------------

PROBLEM:  If you Get a database, Add a new field to that database, and
then Init the database, Genifer crashes.

COMMENT:  This problem was corrected in Genifer 3.02.

WORKAROUND:  Quit out of Genifer before you Init the database.  When you
get back in, it will Init without error.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[7]--------------------------------------------------------------------

PROBLEM: In the layout editor, if you place two fields immediately next
to one another, with no spaces in between, the editor won't let you
insert spaces later.

COMMENT:  This problem was corrected in Genifer 3.02.

WORKAROUND:  Always leave a space between fields.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[8]--------------------------------------------------------------------

PROBLEM:  When you add an additional window to an existing Data Screen,
then regenerate the Maintenance/Inquiry program, the program refuses to
access the new window.

COMMENT:  This is not a bug.  Most likely, you've failed to AutoIndex
your program before generation.  The Autoindex process also determines
which windows are associated with which databases, so you MUST Autoindex
whenever you make significant changes to a Data Screen.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[9]--------------------------------------------------------------------

PROBLEM:  When you Show a Data Screen, variables show as Compute-Yes,
but computed fields show as Compute-No.

COMMENT:  This problem does not affect the application itself, only the
Genifer-generated documentation.  The problem was corrected in Genifer
3.02.

WORKAROUND:  Output the documentation to a File, then edit the file with
a text editor or word processor.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[10]-------------------------------------------------------------------

PROBLEM:  When you Zoom to a screen or report layout, one line of the
screen contains weird characters.

COMMENT:  This is evidently a bug in the Clipper 5.01 compiler, which
Genifer has "inherited."  It is entirely cosmetic, and does not
indicate corruption of the GENDICT.DBF or GENLAYT.DBF files.

WORKAROUND:  If this occurs, just press [Ctrl-End], followed by
[Ctrl-Home].  The screen should then redisplay properly.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[11]-------------------------------------------------------------------

PROBLEM:  If you include spaces in an index expression (for example,
"CR_DATE + BOAT" instead of "CR_DATE+BOAT"), the index expression does
not generate correctly.

COMMENT:  This problem was corrected in Genifer 3.02.

WORKAROUND:  Don't leave blank spaces within your index expressions.
(Remarkable, Holmes!  I never would have thought of that!)

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[12]-------------------------------------------------------------------

PROBLEM:  When you print a hardcopy of Genifer's internal documentation,
sometimes the last couple of lines slop over onto an extra page.

COMMENT:  Genifer respects the page length set in the Customizer, but
ignores the top and bottom settings.  This problem was corrected in
Genifer 3.03.

WORKAROUND:  Decrease your page length in the Customizer by the
necessary number of lines.

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[13]-------------------------------------------------------------------

PROBLEM:  When you delete the last field of a database in the Data
Dictionary, Genifer brings up the first field in the next database.

COMMENT:  This is disconcerting, but essentially just cosmetic.  This
bug was introduced in version 3.03 along with the new cascading delete
feature.

WORKAROUND:  If you find youself in this situtation, just hit Begin, to
move the the first field for the active database (which is what is
supposed to happen).

--------------------------------------------------------------------------


Anomaly Report:  Genifer 3.0

---[14]-------------------------------------------------------------------

PROBLEM:  Genifer crashes with the message "Internal Error 5311".

COMMENT:  This is not a bug.  Genifer, like other Clipper applications,
respects the DOS environmental variable TMP.  SET TMP=D:\SWAP, for
example, causes all virtual memory swap files to be created in the
directory D:\SWAP.  Internal Error 5311 is the result of setting TMP to
a nonexistent directory.

FIX:  SET TMP to a real directory or remove the command from your
AUTOEXEC.BAT altogether.

--------------------------------------------------------------------------

