>>I heard one of my VB programmer friends mention that Visual FoxPro is not fully ODBC compliant. By this he means that, using VB for example, you can open and read a Fox 2.x table, and a VFP free table (one that is not part of a database container). However, VB cannot open a VFP table that is bound into the database container. Apparently too much information about the table is contained in the DBC, and it will either cause an ODBC error or will disconnect the VFP table from the database container, thus losing your long names, persistent relationships, and referential integrity rules.
>>
>>Unfortunately, I do not have VB on my machine, so I can't test this myself. Any truth to this?
>>
>>Bill
>
>maybe you should tell him to download the latest vfp odbc driver

If your friend uses the VFP ODBC driver, then he can open any VFP database or table from VB using the Visual Data Manager (VisData) add-in. Tell him to select File-Open Database-ODBC from the add-in menu, and then look at the driver drop-down list. "Microsoft Visual FoxPro Driver" will be on the list, and he can connect from there to a .dbc or a free table. If he connects to a database, the addin will show all the included tables and their properties. Of course, the interface for this is not nearly as nice as VFP's database designer.