🚀 go-pugleaf

In article <4adlti$d2m@spectator.cris.com>,
Steve Beasley <smbeasle@cris.com> wrote:
>Has anyone ever done this? If so, what is the parameter passing that
>successfully lets the DLL's CRecordSet functionality deal with the
>RecordSet passed from Access Basic? 
>
>I have tested VC++s ODBC abilities and found them to be slow compared
>to Access' direct use of the Jet. I would like to use Access Basic to
>do my Recordset I/O but ... I have some monster calculations that
>would run quite a bit faster in C/C++ and I really don't want to set
>up a user defined structure to pass to the DLL because of the number
>of fields involved. I want to just pass the recordset (or the row it
>is currently pointing to) and let C++ deal with it.
>
>I've got the Access Basic code in place and I have the DLL with the
>MFC CRecordSet functionality in place. I now need for them to work
>together. 
>
>All suggestions are appreciated. Thanks
>
If you are on Windows 3.1 working with VC++ 1.52 and Access 2.0, then the 
DAO RecordSet in Access is not available to outside processes.  ODBC is 
the only way to get at Access 2.0 data.  (This is the official Microsoft 
line, of course.  The DAO2016.DLL exports all the DAO methods, and I'm 
sure there is an undocumented way of calling these functions.)

On Windows 95 with Visual C++ 4.0 and Access 7.0, the Jet Engine is 
available to eveybody who wants to use it.

--
Weiqi Gao
weiqigao@crl.com