You can't use a direct connection (like OLE or by calling entrypoints) from Clipper (16 bit DOS environment) to any Windows DLL or library (32 or 64 bit).
Possible solutions:
- Run an external commandline or config-file driven tool to access the reports (probably a last resort)
- Switch to a reporting library that actually supports Clipper
- Switch to a commercial xBase compiler like XBase++
- Switch to Harbour or xHarbour, the open source Clipper replacement compilers.
Last option is what I would recommend most, ofcourse (I've been recommending this for some years now, an unpaid sort-of 'job', but I'm just a happy user).
Harbour (
and xHarbour (
and
are compilers that translate Clipper code to C and then run a C-compiler to turn that into executable code. Both have a similar featureset, as xHarbour was forked off of harbour. Both are mature and stable environments, but they may take a little time to set up properly (instructions are on the websites). If you would need commercial support, you could go for xHarbour.com, as they offer a subscription model in addition to extra tooling and libraries, both for Windows and Linux.
Both offer better OO-programming models than Clipper, and are easy to interface to OLE and COM components on Windows, and some rather popular libraries like CA-Tools (CT) and NanFor (NF) are almost completely covered by compatible libs.
HTH
TonHu