XPe affects DBF/NDX BDE Access

This may not seem like a XPe question - but since the problem only
occurs on XPe and not XP - I am posting here...

We have a product that uses Dbase3 files *.DBF/*.NDX. It has been
running fine for over 10 years. There are some parts of the system
that use CodeBase (C API library) to access the DBF/NDX files directly.
There other parts of the system (written in VB) that use ADO to access
the DBF/NDX files through a linked MDB table.

We have BDE IDAPI32.DLL v4.0.0.36 installed.

Everything works great when installed on WinNT, Win2000, WinXP, etc.

But - now we have the product installed on Windows XPembedded (XPe).
Again everything seems ok....except one thing.

When the VB app (going through an Access table) adds back in a record,
the apps running CodeBase don't see the new index entry until they
close the table and reopen (or if they scan the index far enough first
to cause a new ISAM page to be loaded). This same test on non-XPe
device works fine.

All other operations (deletes, updates, etc) work as expected.

So I think the problem is that running on XPe has caused the CodeBase
app to not see the change in the NDX file when the new record is added.
If another CodeBase app adds a record - it works fine. So it seems
that it only happens when a new index entry is added through Jet/BDE.

I have gone through the machine to determine if anything else is
different about the installation and I have come back with nothing.

If anyone has any ideas - please post back.

Thanks,
Scott