invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Visual FoxPro

Driver Release Note - File

Visual FoxPro driver 27.0, from 26.0

Build Date Description
26.0.4 22-03-2026 first build of release 26.0
27.0.93 10-11-2026 latest build of release 27.0 at the time of writing

The older end is the first build of release 26.0, not its last, because later builds of 26.0 received ports of changes made for 27.0. The data model of a release is the model that a later build of the same release generated.

  • 5 changes
  • 0 can break a statement
  • 3 groups not available

What Changed, by Group

Every change is in one group: the group answers the question that you ask before you upgrade.

  • Data model
    • –
    • not available
    • Do my statements and views still work?
  • Provider attributes
    • –
    • not available
    • Do I have to change my connection string, provider file or settings?
  • Capabilities
    • –
    • not available
    • What can the driver do with a table?
  • Performance
    • 1
    • Is it faster, and does it call the platform less?
  • Bug fixes
    • 1
    • Is the defect that I met repaired?
  • Enhancements
    • 3
    • What can I do now that I could not?
  • Log-on and platform
    • 0
    • Do I have to log on again, or change something because of the platform?

Download Changes as CSV | Data Model of Visual FoxPro

Before You Upgrade

The data models of this step could not be compared, so changes of tables and columns that break a statement are not known. The data model of this driver comes from build 25.0.17-PROD+5535 in the 26.0 workspace and from build 25.0.17-PROD+5535 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

No other change of this step is marked as breaking.

Top 5 Changes

Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.

Data model

Do my statements and views still work? Tables, views, table functions, columns, parameters, keys, code values, packages and procedures that appear, disappear, are renamed or change type.

Not available. The data model of this driver comes from build 25.0.17-PROD+5535 in the 26.0 workspace and from build 25.0.17-PROD+5535 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

Provider attributes

Do I have to change my connection string, provider file or settings? Attributes of the connection and settings of the driver that appear, disappear or change default or place where they can be set.

Not available. The data model of this driver comes from build 25.0.17-PROD+5535 in the 26.0 workspace and from build 25.0.17-PROD+5535 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

Capabilities

What can the driver do with a table? Whether a table or table function can be selected from, inserted into, updated and deleted from.

Not available. The data model of this driver comes from build 25.0.17-PROD+5535 in the 26.0 workspace and from build 25.0.17-PROD+5535 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

Performance

Is it faster, and does it call the platform less? Paging, batching, caching, filters and projections sent to the platform, fewer requests, less memory.

  • 1 changes
  • commits

Faster and lighter reading of DBF files

Memo fields are read with a buffer of the right size, the selected columns are sorted without extra copies, empty arrays and boxed numbers are reused, and a trim character list is no longer created for every file.

  • importance 2
  • confidence high

Bug fixes

Is the defect that I met repaired? Wrong or missing rows, wrong values, crashes and wrong messages, repaired in a release line that had the defect.

  • 1 changes
  • commits

Date columns of DBF tables are delivered as UTC dates

A date in a DBF file has no time zone. It is now delivered as a UTC date, in the same way as a FoxPro date with time. Before, the date had an undefined time zone, so conversions to local time could shift it by one day.

  • importance 3
  • confidence medium

Enhancements

What can I do now that I could not? New functions and options that are not a table or a column.

  • 3 changes
  • commits

A running FoxPro read can be cancelled

Reading a large DBF table, and reading the headers of many DBF files on a network share, now stop when the statement is cancelled.

  • importance 2
  • confidence high
Files read by the FoxPro driver appear in the managed files overview

The DBF file and its memo file are now registered as read actions with their size, also when the read fails, so that file access can be audited.

  • importance 2
  • confidence medium
Measured throughput figures of the FoxPro driver for estimates

The driver now carries a measured read speed (about 227,000 rows per minute for a full scan) that the engine and progress displays use to estimate how long a read takes.

  • importance 2
  • confidence medium

Log-on and platform

Do I have to log on again, or change something because of the platform? Log-on and token handling, scopes and permissions, a new version of the platform API, retired endpoints and changed limits.

  • 0 changes
  • commits

No changes in this group.

More Information

How This Note Was Made

  • Commit items were classified by one reader; the model changes are derived and need no reading.
  • Commits: the commits of the driver directory in the range that have no equivalent patch in the older state, without merges and version stamps; each was classified by reading its message and change.
  • Model: the NDJSON files of data-models/database of the workspace of each release are compared record by record; only fields that both models have are compared, and texts are counted, not listed.
  • A model generated from a later build of the same release (for example 26.0.340 for 26.0) stands for the release.
  • 11 links between a change and a source commit are recorded.