I think your suggestion of using a different NULL value is a good one. Tank
you very much to all that took the time to help, I was once again reminded
that sometimes the simplest solutions are indeed the best.

Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln., Suite #14
Olathe, KS  66062-4571
(913)829-0888
(913)649-2904 FAX

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bob Thompson
Sent: Thursday, June 06, 2002 11:20 PM
To: '[EMAIL PROTECTED]'
Subject: RE: ERROR CODE 671

Javier,

I believe you can stop the error message by defining the variables that the
user
enters and setting them to NULL before you issue the EDIT command.  If you
do not want the -0- symbol to show in the form, set the NULL character to a
different symbol or space before EDIT and then reset after.

I believe the error message is generated due to the variable not being
defined,
and therefore the look up expression  is not valid.  I do not believe that
the
look up expression has to succeed or actually find a row of data.  (Checking
the "must succeed" box in the variable properties gives a different error I
believe)

Good Luck

-----Original Message-----
From:   Javier Valencia [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, June 06, 2002 10:23 PM
To:     [EMAIL PROTECTED]
Subject:        RE: ERROR CODE 671

Eric,
I figured out that the messages shows because some of the lookup variables
are not found as only some run-time default values are inserted into the
form and the lookups variables are based on data that the user enters when
editing the form. What I really need is a way to capture the error message
so it does not display.

Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln., Suite #14
Olathe, KS  66062-4571
(913)829-0888
(913)649-2904 FAX

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Eric M. Bienstock, Ph.D.
Sent: Thursday, June 06, 2002 9:32 PM
To: [EMAIL PROTECTED]
Subject: Re: ERROR CODE 671

Whenever I get to the line "EDIT USING.." I get the following error:
"ERROR - COULD NOT FIND THE REQUIRED MATCHING VALUE (671)"
=====================

Javier,
Perhaps the error msg refers to a lookup variable in your form.  Check that
all the lookups are succeeding.  If all the values seem to be present in the
form, be sure to check that each of those values came from being looked up,
and not left over from the environment (i.e., clear all the lookup values
before invoking the form).

---------------------------------------------------------------------------
Eric M. Bienstock, Ph.D.
   Database Development, etc.
      Authorized R:BASE Developer
         Eric M. Bienstock & Associates, Inc.
            day: 212-978-7948    eve:  973-763-8650(8)
               FAX:  775-254-2109    [EMAIL PROTECTED]
                   http://mywebpages.comcast.net/ericmb/
---------------------------------------------------------------------------

----- Original Message -----
From: Javier Valencia
To: List RBASE
Sent: Thursday, June 06, 2002 9:50 PM
Subject: ERROR CODE 671


I have an application that inserts a record (with default data) into a file
with an auto number column, gets this record (last record added) and brings
up a form to edit the record. The relevant portions of the code are as
follows:
=====================================
SET ERROR VARIABLE vderr
SET VAR wono TEXT
*(
Some other variable definition, menu code, etc goes in here
)
INSERT INTO wo_file (wo_fy, wo_stat, ih_cont, work_type, sub_sys, +
seg_beg, seg_end, rd_name, district, wo_pvmt, mact_code, mact_eq, +
mact_cq,crew_foreman,crew_size,wo_pstart,wo_pend,wo_astart,wo_aend, +
wcost_labor,wcost_matl,wcost_equip,wo_comments) VALUES(.myyear,'I', +
'I','S',.vdefsub,' ',' ',' ','0 ','N ' ,' ',0,0,' ',1,.#DATE,.#DATE,.#DATE,
+
.#DATE,0.0,0.0,0.0,'None')
*(
wo_no  in the next line is the column that get a sequential formatted auto
number, type is TEXT 8
)
SET VAR wono = wo_no in wo_file where count = LAST

EDIT USING W_wo_form WHERE wo_no = .wono  +
   AT 100 100 920 640 CAPTION 'RMS - MAINTENANCE MANAGEMENT SYSTEM'
=======================================

Whenever I get to the line "EDIT USING.." I get the following error:

"ERROR - COULD NOT FIND THE REQUIRED MATCHING VALUE (671)"

I press the OK key and the form comes up OK with the correct record. The
form has some lookup variables, does not show any errors and works OK when
called from the R Prompt. I though that the error variable "vderr" would
normally catch this error message and not display it. I have tried the
following command:

SET ERROR MESAGE 671 OFF

before the "EDIT USING.." command without any luck. "MESSAGES' and "ERROR
MESSAGES" are set to OFF.
This message it very frustrating as it does not appear to affect the
operation of the application since the offending command (according to
TRACE) seems to execute OK. Any help in getting rid of this command would be
greatly appreciated.
I used to have a database of DOS error codes that Microrim provided to Rbase
developers in the early 90's but It is archived and not easy to get to. Does
anyone have a similar  error code list with descriptions for Windows Rbase?
I am told by tech. support that a list does not exist as such, and that some
of the developers may have compiled their own lists. I for one could use
such list as I often run into cryptic error code when developing
applications. Any chance of getting this list Razzak?

Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln., Suite #14
Olathe, KS  66062-4571
(913)829-0888
(913)649-2904 FAX


================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to