Access / Foxpro / Win NT issue

[Iain]

Hi,

I use Access databases (Access 2000), and have a problem
with tables which look up Foxpro tables.

More recently other staff have been using some of my dbs,
and we've spotted an issue.

Due to historical reasons, we still have some stuff stored
as Foxpro tables, but I've front put an access front end
on this. As a non techie, and the fact that I started out
with Access, I've always preferred Access, and found
FoxPro to be a big pain in the butt in comparison.

Problem seens to be that on machines running Win 2000
there is no problem inputting tables/forms in Access that
are based on the Foxpro tables, but on machines running
Win NT, this doesn't seem to want to work - just an error
message in the Status bar saying *this recordset is not
updateable*.

Is this just an OS issue we're stuck with, or is there a
workaround or solution? (if it was up to me we'd just
import all the old Foxpro stuff into Access and be done
with it)

Cheers,
Iain

 

[Albert D. Kallal]

It is not a OS issue. You need to be running a later version of JET that can
read/write dbase files. The standard Office 2000 install does NOT allow
this.

However, you should be running both the sr1 and the jet updates anyway.
install these updates on all the pc's to ensure that you are running the
SAME version of office and JET.

You can also install the BDE (borlend database engine). access 97 out of hte
box can read/write FoxPro tables. For JET 4 (a2000 and latter) you need to
use the ODBC drivers for FoxPro, or install the updated version of JET.

 

[Cindy Winegarden]

Hi Iain,

Albert mentioned the FoxPro ODBC drivers. The latest drivers are
downloadable from
http://msdn.microsoft.com/vfoxpro/downloads/updates/odbc/default.aspx.

 

[iain]

hi,

thanks for that - all i know is that it works on newer pcs
that we have, which are running W2K, and not on older pcs
running NT.

Iain

 

[Albert D. Kallal]

hi,

thanks for that - all i know is that it works on newer pcs
that we have, which are running W2K, and not on older pcs
running NT.

yes, and as mentioned, this likely means that updates to JET were installed
on the pc's that work. Often, the update to jet can be installed by other
software being installed also.