Product/components used and version/fix level: Natural 09.01.02 Detailed explanation of the problem: Hello, I appreciate getting some clarifying for this situation: NAT0285: Field reference error; reference invalid or missing. This error blocks the “update” in Natural One… or not… I´m not sure.…

this seems to be comparable to what you showed, but it compiles correctly… define data local 1 BUSINESS-FIELDS VIEW OF NCCONTRACT 2 CONTRACT-ID (P6.0) 2 PRICE (P10.3) 2 DID-CONDITIONS (A8) 1 CONTROL-FIELDS VIEW OF NCCONTRACT 2 DATE-RESERVATION (N8.0) /*) imported data fields from Data Defin…

I’m not sure if there is a reason you separated the IN-STATUS field to a separate view or not, but they seem to be on the same file, so can you not just do it as part of the STORE? [image] Tomas Moraes: DEFINE DATA LOCAL 1 BUSINESS-FIELDS VIEW OF FILE1 2 BUSINESS-FLD1 2 BUSINESS-FLD2 2 BUSI…

Thank you! Yes, this seems the same situation… One difference here is that my view doesn’t have fields formatting. I could try this. ( When defining a view its fields doesn’t assume the file’s fields format and size? )

For interest sake can you try changing the MOVE to: MOVE 'I' TO ``CONTROL-FIELDS.IN-STATUS Eugene (Gene) Miklovich ADABAS/NATURAL Systems Support and DBA Cell: 916-202-7047 Normal Hours: 8am-4pm E.T. Please call or text if assistance needed outside these hours.

In this case my business fields are recieved by parameters, and the control fields are managed internally. Before the STORE I want to prevent duplicate records, with READ or even GET using the same business view , regardless the control fields.

Yes, you can let the format/size default to the DDM values. NaturalONE’s edit function to insert fields from a view always includes the format/size (I’ve asked for an option to omit that). define data local 1 BUSINESS-FIELDS VIEW OF NCCONTRACT 2 CONTRACT-ID 2 PRICE 2 DID-CONDITIONS 1 CONTR…

Man, I can’t explain but today it worked fine. I wonder if NaturalOne’s compiler got a new clean session or something like this. I didn’t put format/lenght in the view fields, I put ST1. ... GT1. ... *ISN (ST1.) MOVE 'I' to IN-STATUS UPDATE (GT1.) END TRANSACTION And now I proceed with the w…

Now do what Douglas suggested in his first reply. MOVE ‘I’ TO BUSINESS-FIELDS.IN-STATUS STORE BUSINESS-FIELDS END TRANSACTION Every good Natural programmer knows to avoid unnecessary Adabas calls. Your GET and UPDATE are unnecessary Adabas commands.

Related to this I did another post in the forum. Could you please take a look? Thanks for all. [image] ADABAS field with default Alfanumeric value Product/components used and version/fix level: ADABAS Detailed explanation of the problem: Hello, I appreciate…

Instead of using two views could we define one view with grouped fields? If yes, could you give an example? [image]

[image] Tomas Moraes: Instead of using two views could we define one view with grouped fields? I tried to group but I got this error: [image]

Trouble on referencing *ISN from a STORE

Tomas_Moraes (Tomas Moraes) August 25, 2023, 7:52pm 11

Related to this I did another post in the forum. Could you please take a look?
Thanks for all.

Topic		Replies	Views
NAT3041 in referring file which has new PE and MU field Adabas-Natural , Natural , Natural-on-Mainframes	24	4694	October 23, 2014
Question on ISN Adabas-Natural , Adabas , Adabas-on-Mainframes , Adabas-Basics-on-Mainframes	1	2508	November 22, 2012
Regarding ISN Buffer limit (Adabas Vista Error : +0249). Adabas-Natural , Adabas , Adabas-Add-on-Products , Adabas-Distributed-Data	4	1129	July 24, 2018
ISN of last ADABAS-call Adabas-Natural , Natural , Natural-on-Linux	9	9110	June 7, 2006
Help - Adabas Natural Tecnical Test (Interview) Adabas-Natural , Natural , Natural-on-Mainframes	16	12770	November 6, 2006

Trouble on referencing *ISN from a STORE

Related topics