popup SELECTION criteria (OpenInsight 16-Bit Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 18 OCT 2002 04:34:08PM Steve Carlson wrote:

OpenInsight 16-Bit Specific

In a UI popup , under "selection" tab, I want the selection criteria

to be

"with field=@USER1"

but it will not accept @USER1

How can I do this??

Thanks

Steve C.

At 18 OCT 2002 04:48PM Donald Bakke wrote:

Steve,

You will need to use a little Basic+ to get this to work. @USER1 has no meaning in the UI designer. You can create the popup in the UI designer and then call the popup with the PopUp() function. You would then override the selection criteria with your select statement.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

At 18 OCT 2002 07:00PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Create a symbolic dictionary entry called ATUSER1 with the code

@ANS=@USER1

The Sprezzatura Group

World Leaders in all things RevSoft

At 19 OCT 2002 01:22PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Additionally, if you want to have the dictionary valid in all files, copy the ATUSER1 dictionary to the SYSDICT file. SYSDICT works like DICT.VOC did in ARev.

The Sprezzatura Group

World Leaders in all things RevSoft

At 22 OCT 2002 11:20AM Don Miller - C3 Inc. wrote:

Aha .. the old AREV Dict VOC trick .. in SYSDICT.

I Have ATUSERn… and ATRECURn for all of them. In addition, there are other useful globals as well .. ONE (@ANS=1), including S and G types. Why, in S/LIST G-types are supported .. what a hoot!

Don M.

At 22 OCT 2002 12:23PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Yup, added in G types sometime in mid spring. We also added in support for @CRT and @LPTR. Confused me once because I forget it was there :)

The Sprezzatura Group

World Leaders in all Things RevSoft

At 22 OCT 2002 02:44PM Don Miller - C3 Inc. wrote:

Whatever happened to the Parser mods I did for you a long time ago .. Interactive Queries for the Limit Clause? I can't upgrade to your current version because my Parser is different from your current release. Also, did you fix the Limit clause to allow for more than 1 Limit (e.g., a limit stack)? If so, how do I replace my bastard .. ur… altered version of the parser with your current one in your latest 16-but upgrade???

Don Miller

C3 Inc.

View this thread on the forum...