Bob, This is indeed the case; however when I do the row insert in the previous command I can also pre-set some of the fields with run-time values, some of the lookups depend on data that the user enters (edits) when using the form. I guess what I am really looking for is a way to trap the error message so it does not display. My best solution so far is to create a dummy record so the lookup will not fail.
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 10:49 PM To: '[EMAIL PROTECTED]' Subject: RE: ERROR CODE 671 Javier, I have run into this same error message before. In my case I have always found that it was caused by a look up expression in the form that uses a variable in the WHERE statement and the variable was not defined before executing the form. For example, in the form a variable could be defined as: Var_X = LEGEND in DEFTAB WHERE ID_COL = .Var_ID If Var_X field properties are set to where data entry or edit is NOT allowed and variable Var_ID is not defined before executing the form, you will definitely get the "Error - Could not find the required matching value" error. You may have checked this scenario, but I am certain that the above will give that error message. -----Original Message----- From: Javier Valencia [SMTP:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:51 PM To: List RBASE 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 << File: ATT00000.html >> ================================================ 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/
