ctl3dv2.dll (OpenInsight 32-bit Specific)
At 27 NOV 2002 11:54:28AM Warren wrote:
Okay, I downloaded the OI32 demo and got a trial SN. I installed it on a Win98SE workstation. When I try to open the report designer it crashes with a complaint about ctl3dv2.dll not properly installed in the window system directory. System has to be rebooted after this.
I moved the dll from the OI directory to the system folder (replacing the version there). After rebooting, I still get the same problem. I tried installing the OI32 client also, same problem.
What's the trick of getting this to work?
At 27 NOV 2002 12:22PM Revelation Software Technical Support wrote:
Warren-
Does this thread address your issues?
At 27 NOV 2002 12:24PM Donald Bakke wrote:
Warren,
You may indeed have a bad ctl3dv2.dll file, however, Reporter will not run on Win98SE and OI32 per documentation and several posts online.
dbakke@srpcs.com
At 27 NOV 2002 02:04PM Warren wrote:
Not a works member, unfortunately :)
At 27 NOV 2002 02:06PM Warren wrote:
Ah, ok. Guess that kind of frosts migrating from ARev 3.12 to OI32 as will have to factor upgrading Win98 to W2K or XP workstations.
At 27 NOV 2002 02:10PM Warren wrote:
Will reports run in Win98? That is can I design reports on a W2K workstation and users run them on Win98 workstations?
At 27 NOV 2002 07:57PM Donald Bakke wrote:
Warren,
Yes you can run reports, just not those designed with the Reporter. Personally, I don't recommend the Reporter because of its history of problems. Many here do use it and, I presume, are happy with it but we build all of our reports using the OIPI, S/List (from Sprezzatura), and DirectPrint (from Splaver Software). You might be very interested in DirectPrint if you are doing an AREV conversion since this allows you to use your legacy code, especially if it is printer specific, with minimal changes. If you are looking to use true Windows printing then the OIPI and S/List is your best best, but this will require more programming to convert legacy code.
dbakke@srpcs.com
At 28 NOV 2002 12:25PM Warren wrote:
Thanks for the info.
At 28 NOV 2002 12:38PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
A second endorsement for DirectPrint - used it at a sites a few weeks ago. Only wish we'd had it a few years back, it makes converting legacy printing programs a doddle!
World Leaders in all things RevSoft
At 28 NOV 2002 01:00PM Donald Bakke wrote:
…it makes converting legacy printing programs a doddle!
I assume "doddle" is British speak for "easy task"?
dbakke@srpcs.com
At 28 NOV 2002 01:36PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Yup indeed
World Leaders in all things RevSoft
At 02 DEC 2002 11:54AM Warren wrote:
Naturally we're dealing with systems that were developed either in RevG or early versions of ARev and migrated/updated.
As such reports run from MERGE, FORM, EW, in-house template driven report generators and RBasic code using HEADING/FOOTING/PRINT/PERFORM statements, and TCL VOC entries.
Anything to ease the migration process would be helpful.
Are there any tools to help migrating WINDOWS/TEMPLATE collector and data entry screen? With dozens of multipage screens with commuter logic behind them is not fun task to repaint from scratch.
Thanks.
At 02 DEC 2002 12:18PM Donald Bakke wrote:
Warren,
Are there any tools to help migrating WINDOWS/TEMPLATE collector and data entry screen?
I believe Sprezz wrote a utility that does something like this. If they don't respond you may want to send them an email.
dbakke@srpcs.com
At 02 DEC 2002 02:31PM [url=http://www.sprezzatura.com" onMouseOver=window.status= Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
We do indeed have one (along with a utility to run MERGEs under OI, and obviously LIST commands) but then again so do several other people. If you're having to do more than one conversion it becomes worth while writing one. We use it to help soften the blow of conversion charges from AREV to OI! Rewriting every screen from scratch CAN be a pain. That having been said, promoted events (like your Frameworks Don, and our own internal equivalent) can make aplications development so much faster that sometimes it just isn't worth doing the conversion!
World Leaders in all things RevSoft
At 02 DEC 2002 04:11PM Donald Bakke wrote:
…so much faster that sometimes it just isn't worth doing the conversion!
Exactly. It's really hard to explain sometimes to customers that even if we had a conversion utility (which we don't have or use) we would probably spend as much if not more time changing it so it looked right in a Window's world and that the functionality complied with an event-driven paradigm. Then to make sure it functions within the OI application's infrastructure just adds more work.
Nowadays we run a report that displays all the prompts, dictionaries, processing logic, validations, conversions, defaults, etc., information. We then design our OI forms based on this information and a visual screen shot of the original AREV form as a guide. It's about the fastest way for us to design forms.
dbakke@srpcs.com
At 02 DEC 2002 05:00PM dsig@sigafoos.org wrote:
Oh yeah .. Arev is your friend .. use DocWindow, DocMenu .. print it out then use it as an outline.
Conversion routines, though handy for a first pass, are not the final solution. You really have to rethink (that is, of course, assuming
Arev into OI.
Naming conventions etc .. especially if you are going to be playing with Promoted Events .. a little of fore work will make live much easier as you go down the path.
dsig@sigafoos.org onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"
David Tod Sigafoos ~ SigSolutions
Phone: 971-570-2005
OS: Win2k sp2 (5.00.2195)
OI: 4.1.2