Valores de fstat

Fstat

fstat is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction.

Syntax

fstat

Examples

# MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL
# Create a record in the table MYTABLE with they key value 1 if it doesn't exist 
Local File MYTABLE [MYT]
Read [MYT]KEY1=1
If fstat
   [MYT]KEYVAL=1 : Write [MYT]
   If fstat
      MSG="The key was created in the mean time"
   Else
      MSG="Key created"
   Endif
Else
   MSG="Key already exists"
Endif

Details

fstat is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error:

In a sequential read (Getseq and Rdseq), fstat is set to '1' at the end of the file.
On Lock, fstat is set to '1' if the lock could not be performed.
For a database operation (Read, Look, Readlock, For, Write, Delete, Rewrite, DeleteByKey, and RewriteByKey), the error statuses are from 1 to 7, as shown in the following table.

Note that the use of literal numbers should be avoided: dedicated constants exist for this purpose.

Constant	Value	Explanation
[V]CST_AOK	0	Operation succeeded.
[V]CST_ALOCK	1	Record is locked.
[V]CST_AOUTSEARCH	2	In <= or >= read mode, indicates that read succeeded, but the key found is not equal to the value.
[V]CST_ADUPKEY	3	Duplicate value on unique index.
[V]CST_AOUTKEYS	4	Attempt of reading a key value that is smaller or greater than all existing key values.
[V]CST_ANOREC	5	Record not read (no current record exists).
[V]CST_ARECTICKUPD	6	Update conflict: the line no longer exists with the right updtick value (concurrency error during an update operation).
[V]CST_ARECTICKDEL	7	Delete conflict: The line no longer exists with the right updtick value (concurrency error during a delete operation).

Entradas populares de este blog

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente: https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor: https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending through meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending through Workflow 4) Sending through ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is meladx executable file, that you can find in runtime\bin directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES” go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail ...

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen: https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to. If you have a better way, please share. Add column to PORDERQ; YLINTEX2, Type TXC Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....