Approach doesn't have its own proprietory database format. It can connect to most backends but dBase IV is the default. The .apr file contains connections, views, scripts etc. If using dBase format there should be separate .dbf, .dbf and .adx files containing data, memo fields and indexes respectively.
If using dBase IV you can connect to the tables using the MS ODBC driver. Only problem is that Approach uses a proprietory index format (.adx files) so you may only be able to open the table exclusively for write access or maybe read-only if the driver requires the table to have a primary key. The ODBC driver will expect to find a dBase index (.mdx or .ndx). Write operations from VB are always problematical because they don't update the adx files and screw things up for Approach users.
Approach is also an ActiveX server and it may be better to automate it and access the data through the Approach object model.
Please explain exactly what you want to do and I'll advise the best strategy.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.