At 08:38 AM 1/3/2004 -0500, Mark Kwoka wrote:

Hello rbase friends,

here is my problem, perhaps anyone can help.

In Rbase 6.5++ Application Express one of the available actions is EDIT USING formname. The user can enter a comparison value to edit a specific row of data by typing the following in the WHERE clause: &&&&..WHERE columnname = @message.

If I use the same idea in RBASE 7.0 I get an error message Column or variable @messagenot found (2515). Maybe this will not work with 7.0 as it did with 6.5++?

Any idea what is wrong?

Mark,


A complete new GUI interface and Application Designer in
R:BASE 7.0 for Windows includes the option "Custom Actions".

Application Designer > Actions > Add > Custom Action

That's where you would use the pre-defined and fully
tested custom action to achieve the same goal.

You can also take advantage of new DIALOG command to
provide your end-users the option and the ability to
test as well as provide custom messages, etc., before
using the EDIT USING formname option.

There are a lot more options in Application Designer
to take advantage of.

Enjoy and make sure to have fun!

Very Best R:egards,

Razzak.

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [EMAIL PROTECTED]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: Send a plain text email to [EMAIL PROTECTED]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [EMAIL PROTECTED]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, place any text to search for.
================================================




Reply via email to