{{tag>category:"OpenInsight 32-Bit" author:"Jim Vaughan" author:"Mike Ruane"}}
[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]
==== Upgrades (OpenInsight 32-Bit) ====
=== At 01 JUL 2003 05:43:46PM Jim Vaughan wrote: ===
We have a single user application that we distribute using the run time license.
We for the first time have some users that want to run this application in a multi-user environment and they need to apply an SDP.
Up until now I have handled all the distribution and upgrading of our users systems. I use Installshield for the initial install and then custom code in OI to handle upgrades. Occasionally an upgrade requires that I use a full release with an Installshield installation and this is how I handle an upgrade to OI.
How do I upgrade the user and preserve his application of a SDP? What do I not overwrite, is it just OENGINE.DLL?
If this is the case when Revelation releases an upgrade to OI and this updates OENGINE.DLL how do upgrade his OENGINE.DLL?
----
=== At 01 JUL 2003 05:50PM Mike Ruane wrote: ===
Jim-
The licensing is embedded in Oengine.dll.
We have functions that transfer license information from one version of the software to another.
Thanks-
Mike
----
=== At 01 JUL 2003 06:00PM Jim Vaughan wrote: ===
That's what I thought so how do I upgrade the users OENGINE.DLL?
----
=== At 01 JUL 2003 06:08PM Jim Vaughan wrote: ===
Did you ever get a chance to look at two bugs I reported?
(1) ODBC driver (non-integer value retuned from a datetime calculated field cause the odbc driver to crash)
(2) OLE multiple indexes (Pat said he had this fixed in 4.1 and 7.0 source trees)
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=FA10370E8EF21D9D85256D5600775D20|View this thread on the Works forum...]]