, , ,

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

Verifile in edittable (OpenInsight 32-Bit)

At 13 DEC 2010 09:53:10AM Michael Matthews wrote:

I have a column in an edittable with a verifile () validation pattern. I'm also calling a popup to stuff the value of one cell of that column. The popup returns a key from the same tablename as the verifile. The cell is populated properly, but when leaving the cell, I get the message about the entry needing to be a key in the tablename table, even tho the value came from the table!

Does anyone know a workaround, or why the verifile is acting funky?

Gracias,

Michael


At 13 DEC 2010 04:27PM Barry Stevens wrote:

What happens when you just enter the same key that you had returned from your popup, if that works, then you need to check how you are stuffing the cell with the popup value, debug to see the 'real' value returned.


At 13 DEC 2010 04:56PM Sean FitzSimons wrote:

Michael,

What version are you using? Barry has made a valid point and I am curious as to what method you are using to populate the edit table after the return from the popup.

Sean


At 14 DEC 2010 08:38AM Michael Matthews wrote:

OI V 9.2.

There is a verifile validation and an OCONV (L#######-###) on the column. When I type in a key to the referenced table, it accepts and OCONV's properly. When I select from the associated popup (from OPTIONS), it stuffs INVALUE with the key, does the OCONV and accepts the value, but puts up an error message about needing to be a key in the referenced table. If I take off the verifile and try to do the same thing in the event handler, it accepts the value but inserts an extra '-'.

Curiouser and curiouser..


At 14 DEC 2010 11:49AM Sean FitzSimons wrote:

Michael,

Is the key to the referenced table in the OCONV format or the ICONV format?

Is it possible to post your OPTIONS event code or email it to me at [email protected]?

Thank you,

Sean


At 14 DEC 2010 01:41PM Michael Matthews wrote:

Thanks, Sean.. I have a workaround now. I am running into a number of other edittable-related issues though.

View this thread on the Works forum...