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

At 02 JUL 2020 12:32:31PM rdhull50 wrote:

I have a form that I use for Display-only purposes. The only control that is enabled is the record key as I do not want the user to make any changes.

If I enter a record key in the enable prompt (ID), then the record is not READ and hence not displayed.

If I select a record from a popup, then it is READ and does display.

The only way that I have found around this is to Enable another control and make it read-only so that the cursor will move to this next enabled control and cause a READ on the row.

Is there some other way of doing this on the enabled record key control instead? I have tried various Quick Events but have not found one that will work and there doesn't seem to be a property on the ID control that I can set to do it either. Maybe what I'm doing is the most efficient anyway?

Robert Hull


At 02 JUL 2020 12:44PM Andrew McAuley wrote:

The issue is that it is the lostfocus that tells OI you've finally entered the key. As you only have one control there is nowhere to lose focus to.

You COULD put a quickevent on the CHANGED event that fires a READ but if you typed 207 you'd see row 2, then row 20, then row 207. Or you could add a button next to the key control labelled "Read row" which did nothing other than provide a landing spot for the focus?

I guess the question is "how would a human know you'd finished typing?". Once we know that we can look for software solutions!

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft


At 02 JUL 2020 12:50PM rdhull50 wrote:

I guess what I'm doing now …. enabling another control but setting it to read-only is probably the best solution. It is essentially the same as you suggested with adding the "Read Row" control.

The control I picked is actually a symbolic field that the user wouldn't try to change anyway.

Robert Hull

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/acd60f8598ce5843a38714a6f0c9e342.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1