, , ,

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

PAT_CHECK line number 1 (OpenInsight 32-Bit)

At 11 SEP 2007 10:07:39PM Jim Vaughan wrote:

Anyone ever seen an error like this before?

PAT_CHECK line number 1

Call Stack

PAT_CHECK line number: 1

OIWIN_SYSMSG line number: 1

$$$SYSPROG*VALIDERR..OIWIN* line number: 56

RUN_EVENT line number: 1

SEND_EVENT line number: 1

DATA_VALIDATION line number: 1

$$$SYSPROG*LOSTFOCUS..OIWIN* line number: 53

RUN_EVENT line number: 1


At 12 SEP 2007 07:06AM Mike Ruane wrote:

Jim-

PAT_CHECK is an Arev32 Patern checker.

From the header:

* VERSION : AdvRev 2.0

*

* PURPOSE : Pattern Parser to allow rendering of complex patterns into

* natural language text for user interaction.

*

* AUTHOR : B. Anderson

*

* CREATED : November 19, 1990

*

Where are you seeing it?


At 12 SEP 2007 10:11AM Jim Vaughan wrote:

One of my users (using a runtime) in the latest release of my software is seeing this error as focus is lost on a editline. The editline has a validation of (-9999999,9999999) and no conversion.


At 12 SEP 2007 10:40AM Jim Vaughan wrote:

… and I am not using AREV32.


At 12 SEP 2007 03:47PM Jim Vaughan wrote:

I just tested validation on a form using my system.

If I tab away from a control.

Running with my development OENGINE.DLL it works OK.

Running with the run time OENGINE.DLL no validation occurs at all.

Validation is (-9999999,9999999) and no conversion on an editline.


At 12 SEP 2007 05:14PM Jim Vaughan wrote:

Actually I get the same error as the user, see end of post.

However I only see the details of the error if I am using my replacement debugger (which is what the users see). If I have the normal OI debugger running I get a ding and no validation.

So what the !@#$ is wrong with numeric validation? Why is it not working when running with a run time engine? What do I do to fix this?

Error as shown by my replacement debugger follows:

PAT_CHECK line number 1

Call Stack

PAT_CHECK line number: 1

OIWIN_SYSMSG line number: 1

$$$SYSPROG*VALIDERR..OIWIN* line number: 56

RUN_EVENT line number: 1

SEND_EVENT line number: 1

DATA_VALIDATION line number: 1

$$$SYSPROG*LOSTFOCUS..OIWIN* line number: 53

RUN_EVENT line number: 1


At 13 SEP 2007 07:10AM Mike Ruane wrote:

Jim-

Can you email the engine to me? Rename it as oengine.dlx or something.

The reason I ask is that I cannot duplicate it here. I installed a new OI 8.0.1 with a dev serial number. I made a form with three edit lines, with validations of (-999999,999999), (-99999,99999),(-9999,9999) and tested it; it worked. I made that form the application entry point.

I then stamped the engine as a runtime, and fired up the system. The validations all still worked.

Thanks

Mike


At 13 SEP 2007 10:04PM Jim Vaughan wrote:

Thanks Mike the new runtime engine fixed it.


At 14 SEP 2007 11:14AM Warren Auyong wrote:

It would be interesting to see if this also solves your problems with REPORTER.


At 16 SEP 2007 05:38PM Jim Vaughan wrote:

It will indeed, I am waiting to hear back from the customer.

View this thread on the Works forum...