Denis wrote:

Maybe it is corrected with 2003

Take a look at the components involved.

The data source is the Excel workbook. The MS product in question is
the Office suite. The latest release version is Excel2003. Development
for Office is on going. From what the NDAs (I'm not one of them) have
let on we can expect an enhanced future version of MS Access (but don't
hold out much hope for your Excel wish-list <g).

The SQL engine is Jet. This most recent version is Jet 4.0,
approximately contemporary with Office2000 but is not directly linked
with Office development. Jet development has been discontinued; Jet no
longer ships with MDAC (since MDAC 2.5). The Jet development team has
long been disbanded. Jet 4.0 service packs have continued to be
released (to 2004) to address security issues. We are told a Jet team
has been formed for the version of MS Access currently under
development but not the extent of their remit. I would guess they are
working on further security enhancements only.

The link between the data and the engine is the OLE DB provider. It is
also part of Jet. The most recent Jet provider is the Jet 4.0 version.

The memory leak is caused by a bug in the OLE DB provider. I do not
expect this to ever be fixed. It certainly wasn't fixed for the release
of Office2003. A fix for the next MS Office release is possible but
extremely unlikely: MS Access's new Jet team are unlikely to prioritize
fixing a bug which only causes problems when the data source is Excel.
Jamie.

--