
Anomaly Report:  GenRun 1.0

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

PROBLEM:  If you do a Retrieve in a scrolling window, then press [Esc]
to abort, the window is not properly redrawn.

COMMENT:  This was corrected in version 1.01.

WORKAROUND:  If you then press [PgUp] followed by [PgDn] (or vice
versa), the entire window is repainted.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  If you validate a field against a field with a different name,
GenRun crashes when you try to add or modify records with the message:
"(b)DEFINESCR, Error 14, Variable does not exist".

COMMENT:  This was corrected in version 1.01.

WORKAROUND:  You should only validate a field against a field of the
same name.  If you absolutely need to validate against a differently-
named field, and are using GenRun for development only, omit the
validation during the debugging process and add it back in just before
you generate code.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  If you put computed fields on your data screen, GenRun crashes
with the message: "Procedure DEFINESCR line 458, Error 7, Syntax error".

COMMENT:  This was corrected in version 1.01.

WORKAROUND:  If possible, use variables instead of computed fields.  If
you must have computed fields, and are using GenRun for development
only, specify the field as Say (rather than Compute) on the screen and
switch it back to Compute just before you generate code.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  You have a database which has been working fine with your
dBASE IV or Arago application, but when you try to access it, GenRun
crashes with the message "Error DBFNTX/1012  Corruption detected".

COMMENT:  You're probably using a dBASE IV or Arago database file which
contains a memo field.  In GenRun 1.02, this situation produces a
message that the database is not in standard .DBF file format, rather
than causing GenRun to crash.

DISCUSSION:  As you may know, FoxPro and dBASE IV store memos in a
format different from the dbase standard (i.e., that used by dBASE
III+). Since GenRun will only work with files in the standard format,
this presents a minor problem if you wish to use existing dBASE IV or
FoxPro files which contain memos.

If you're simply using GenRun as a test environment while you develop or
modify an existing application, just rename the existing databases files
and INIT them again inside Genifer.  The files will be recreated in
standard .DBF format.  (During testing, you probably don't want to work
with live data anyway.)

If you really need to use the existing data, you may convert the files
to standard format with the COPY TO command.  Rename the existing file,
run dBASE IV (or Arago), USE the renamed file, and then issue the command:

                    COPY TO <file name> TYPE DBMEMO3

In FoxPro, the procedure is the same, but the command is:

                    COPY TO <file name> TYPE FOXPLUS

Finally, if you have somehow inherited a dBASE IV file, but don't
actually have dBASE IV itself (or FoxPro or Arago, as the case may be),
you can use Genifer to convert the file.  GET the structure of that
file, delete the memo fields in the Data Dictionary, INITialize the
file, add the memos back, and INITialize again.  This method will
destroy any data currently contained in your memo fields, but all other
information will be preserved.  This method will also work only if you
have Genifer 3.02 or later.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  You have a database which has been working fine with your
FoxPro application, but when you try to access it through GenRun, you
get the message "File XXXXXXXX.DBT is missing"

COMMENT:  See the discussion in [4] above.  The limitation described
there still exists in GenRun 1.02, but the error message is somewhat
more informative.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  If you select Set from the Filter menu, and try to cursor past
a logical field, GenRun crashes with the message "Argument error INSTR".

COMMENT:  This problem was corrented in version 1.02.

WORKAROUND:  Avoid using this feature if your screen contains logical
filter fields.  It will work properly when you actually generate code
for your dbase compiler/interpreter.  All other portions of the Filter
system are unaffected.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  When you run a maintenance program, it paints the screen but
then crashes with the message "Error BASE/1002  Alias does not exist."

COMMENT:  You have probably added a new file validation to an existing
maintenance program, and then run the application without AutoIndexing
again.  This problem was corrented in version 1.02.

WORKAROUND:  AutoIndex the program.  You should see the new validation
file added to the database list.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  The syntax of the INLIST() function in GenRun does not match
the syntax in FoxPro.  Where GenRun wants an expression such as:

          INLIST(month, "April,June,September,November")

FoxPro expects the format:

          INLIST(month, "April","June","September","November")

COMMENT:  In GenRun 1.02, INLIST() accepts either variation.

WORKAROUND:  You can use the following constuction in place of INLIST():

          (","+month+"," $ "April,June,September,November")

This expression will work in either the GenRun or FoxPro environment.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  When you try to List, Add to, or Delete from G_FILTER.DBF,
GenRun crashes with the message "No exported method: OSCODE".  This same
message may be encountered when you press [F1] for help.

COMMENT:  This problem was introduced in GenRun 1.02.  It was corrected
in GenRun 1.03.

WORAROUND:  None.

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

Anomaly Report:  GenRun 1.0

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

PROBLEM:  When you try to run a maintenance, inquiry, or report program,
GenRun crashes with the message "Procedure SETFIELD line 69, Error 2,
Bound error, array access".

COMMENT:  There are two possible causes.  You may have an index which
contains either a nonexistent field (usually a field which was created
at one point in the development process and then subsequently deleted).
Alternatively, one of your indexes contains a function as part of the
expression, but the Allow Autoindex flag is set to Yes.  Whenever an
index expression contains functions, you must set Allow Autoindex = No.

WORAROUND:  Check all the indexes in the Data Dictionary for these two
problems, and correct them where necessary.

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

