I have been spearheading the effort to convert our AREV apps into OIv3.4. I am trying to deploy a runtime application and run it. . So far, things have not been easy. First, I kept getting the "too many users" message. The VXD driver was supposed to fix it, but to no avail. The development copy would run, but not the runtime. I had to install OI3.1 from my original CD, and apply the 3.2, 3.3 and 3.4 upgrades. Then I brought in my application via APPBACKUP, and got it running. After deploying the runtime, it worked, after a fashion. I am deploying the SYSPROG application, with a defined entry point that works in the development system. When started using the runtime engine, the entry point doesn't enter, the app goes nowhere. Tech support is looking into it, but said it was designed to have an application other than SYSPROG for a starting point, so I did that too, and got the same result. It just won't start. I can run the EXAMPLES application when deployed as runtime, but not an app that accesses AREV files.

Also, the runtime engine doesn't seem to remember the users I set up in that application before the deployment. So I always get a window that prompts me for the username, and says the one that should work is unknown to the system. And another thing, as a test, I defined a file JUNK from the development side, which was put by default into DATAVOL. I copied the SYSPROG.DBT file to the runtime directory, as recommended in "Updating a deployed OpenInsight application", by Darren McGurran. But apparently, the runtime engine does not have a DATAVOL. I don't know why, but the directory in the runtime directory is called DATA, not DATAVOL. So, I am pulling my hair out trying to figure this all out.

I have seen some of the problems you're talking about myself.

Here's a suggestion for you. Copy the entire OI development directory structure intact to where you want the deployed application to be. Replace the engine and the reporter with the run time copies. That's it . Now you have a deployed copy with less hassles and everything is in the same place.

It might not solve all your problems but it will cut down on the headaches!

Hope this helps.

The "Runtime Deployment Kit" book says that you should be able to run LB.EXE to add, remove, delete or modify users in the runtime app. However, when I run it (from the runtime directory) I get a window with the title "DataBase Manager Engine Initialization" that says "No Server". Another thing that does not work as advertised.

Workaround: In the development system, Use Check out entity, select Application rows, select SYSENV:USR_SYSPROG. It copies into the runtime and the runtime sees the users from then on.

Ron,

LB.EXE hooks up to the engine. It needs the engine to be running and it needs some information to securely connect. Try:

<code>
oengine.exe  /un=
lb.exe /ap= /un= /pw=

</code>

For example:

<code>
oengine.exe myapp /un=admin
lb.exe /ap=myapp /un=admin /pw=topsecret

</code>

Cameron Purdy

info@revelation.com

—————————–10992802310320–

Thank you sir, it works!

View this thread on the forum...