Forums

by Scott Gavin >> Fri, 14 Sep 2007 2:24:47 GMT

I am to create an application in a subschema of the JccCoreReportSchema, By default there is a UKReportSchema in existence, this will be my RnD schema.

Of the application object, I have created a method that calls startupJccSchema, also trying startupJccRepSchema (mimicking existing application initialization method calls).

Debugging I can see that my Initialization method is not being called before several forms are quickly painted and vanish ending execution.

I have setup my application exactly like the startup application in the JccCoreReportSchema.

Are there other settings I am not aware of or may have overlooked?

Regards,
Scott.

by BeeJay >> Fri, 14 Sep 2007 3:33:12 GMT

There are a number of things that could be preventing an application from starting. A few potential candidates that immediately spring to mind are as follows (this should not be considered a definitive list):

1. Global::getAndValidateUser implementations could have code in them to only allow certain named applications or only allow applications running from certain schemas to be run.

2. If the application is running as a thin client, the EnableAppRestrictions and associated options can be used to only allow certain applications, or applications from certain schemas to be run.

3. The initialize logic you are inheriting from superschemas, such as JCCSchema etc, could be deciding to terminate the application. eg: If application defined security requirements are not met.

I'd start by checking the jommsg.log files on the DbServer, AppServer and the local thin client machine to see if anything obvious shows up there.

If not, try implementing Global::getAndValidateUser in your UKReportSchema and put a MsgBox right at the beginning of the method. Ensure you have the JadeUserInterrupt available and turn on method tracing to see if that helps identify the methods that are executing that could be causing an early termination of your application.

If none of this helps, you may want to consider contacting your appropriate client support representative for further advice on whether or not there are any potential JCC Application specific situations that could result in this early application termination behaviour.

Cheers,
BeeJay.