Using 7.2.2, I am trying to create a runtime version of the application. All works well except for the following:

1. Any user names created to use the application while using the full development version do not transfer over during the deployment. For example, I had a user name CDC for my BFS application and it is not available. The only way to login is to use the application name (BFS).

2. When I try to log into the SYSPROG account for the deployed application, I get a message saying that No Entry Point was created for SYSPROG. What entry point would I / should I use?

Thanks.

Charlie

This is a quick fix for both of your problems…

Warning!!! "oengine.dll" is critical for both runtime and development applications. Do not delete or modify this file! Only rename it.

1) In the deployed application, rename the "oengine.dll" to "oengine.run"

2) Copy from your development application to the deployed application "oengine.dll"

This will allow the deployed application to act as a development application so that you can fix the user problem. This will also preserve your "runtime" "oengine.dll"

Once you are done with the fix, then just remove the "oengine.dll" and rename the "oengine.run" to "oengine.dll". This will return your deployed application to a runtime state.

Charlie,

Richard Hunt already responded to your first issue. What he didn't mention (but it was implied) was that Users are not deployed when creating runtime applications.

2. When I try to log into the SYSPROG account for the deployed application, I get a message saying that No Entry Point was created for SYSPROG. What entry point would I / should I use?

By replacing your runtime engine with a developer engine (as Richard suggested) the above problem goes away because OpenInsight won't be forced to log in as a runtime application. You got that message because SYSPROG does not have a default window for an entry point. By replacing the engine (temporarily) you can now open SYSPROG in development mode which takes you to the Application Manager.

[email protected]

SRP Computer Solutions, Inc.

Thanks Don

Thanks so much Richard for your assistance.

View this thread on the Works forum...