Gino, to emphasize a point in the the previous replies: From the information included in your post, it sounds like you have not used VFP's database engine at all, but rather have measured the Jet ISAM driver's speed at processing a Foxpro table and compared that to Jet's speed at reading an MDB.

I can promise you this: If you compare the speed and flexibility of VFP's database engine (using its native tables) with Jet (using its native tables), Jet won't come close, especially when you go above, say, 200K records.

Here is a reply on this topic from a company that specializes in both VB and VFP C/S solutions.

> There is no comparison between the access speeds of VFP and VB. VFP is
lightyears faster on every operation, even with largest data sets and VB using
the fastest RDO statements. The only reason we program in VB/ODBC is because
some of our clients are a little uncomfortable with VFP and prefer a more
"mainstream" solution such as VB/SQL-Server.
>
>(name omitted)
> Senior Software Engineer
> VisualSoft, Inc.