VISTA Release Notes Version A.07

A.07.29 VISTA No longer overwriting lines when printing stdlists.

A.07.31 VISTA Increased maximum extracted record size to 500 with "VIEW ALL" .

A.07.32 VISTA Removed loop that occurred when extracting pages based on a search by

index.

A.07.33 VISTA Resolved garbage being displayed within a sub report.

When extract by lines was selected and heading lines were specified. Also resolved

loss of tab key when exiting a sub report that was created by extract records.

A.07.34 VISTA Fixed mixed-case Search bug in NM code.

A.07.35 VISTA Will now reindex search indexes with leading spaces.

A.07.36 VISTA SHEETMATE PC downloads now work.

Spoolfile number was recovered incorrectly. Spool file names from 'REMOTE PRINT' are now

correct.

A.07.37 VISTA Multiple printer Groups now work.

Addressed obscure string and column search bugs.

A.07.38 VISTA Fixed a Page Security problem.

When Field was NOT on every line, it caused INDEXREPORT to not find the proper number of pages.

A.07.39 VISTA SAVE REPORT fixed, bogus msgs suppressed.

Fixed Save report with blank filename abort.

A.07.40 VISTA Default sorting of archived reports was not working correctly when sorting

by dates.

A.07.40 VISTA When down loading with SheetMate, pass new Sheetmate commands into

usefile. The new commands added are MAP and MAX@.

A.07.40 VISTA Fixed printing from within VISTA.

Printing was broken when form feeds were removed. A new flag "$NO'FORCE'PAGE'EJECT" was

added to VISTAINI.DATA.NETBASE to enable this behavior. When this flag is set to ON normal

printing within VISTA will not work correctly.

A.07.41 VISTA Fixed bugs in Page index rebuilding.

Modified VISTA base DBPUT logic to abort if unexpected error detected.

Fixed sorting of Report Profile entries for windows client.

Optimized indexing operation when VSAVEing to an existing, very large folder.

A.07.44 VISTA Misc. fixes

Printing from the Client will now retrieve the forms message information for the report being

printed.

$SORT-FOLDERS had been globally disabled and is now functioning.

In the Client, the indices now correctly report the proper line number. Previously it was off

by one.