Karbon wrote:I'll give you a hint with the OCX.. Just use OpenLibrary and CallFunction on it. An OCX is nothing more than a regular DLL with an ActiveX wrapper (and you can just not use that).
Karbon wrote:What I do is pass in an ID for the document I want to print and use ReportMan's internal query capability to pull data sets directly from an ODBC connection (which ReportMan supports natively).
WOOHOO! Thanks very much for that!
I had actually started to try the way you had mentioned earlier (using the Interface generator) before I gave up due to the query issues. Glad to know I can just treat it like a DLL!!!!
I should add that I've had problems with this setup. Namely "unknown error" popping up from within ReportMan. Since the error message is so specific I can't really debug it. It doesn't seem to happen often but it happens often enough for a few dozen people to have reported it already. IF they just pull the report again it seems to clear up quickly but it's sure annoying. One reason I switched to a 3rd party tool is that printing and such was so unreliable using webgadgets. It doesn't seem like I've improved the situation all that much so far.
I've been working with Toni (author of ReportMan) to get some work done in there so be on the lookout for a new release soon. A little financial motivation goes a long way
Karbon wrote:It doesn't seem like I've improved the situation all that much so far.
I can relate to that!
Karbon wrote:I've been working with Toni (author of ReportMan) to get some work done in there so be on the lookout for a new release soon. A little financial motivation goes a long way
I can relate to that!