Services Partners Company
Knowledge Base


Article

4GL/ABL: How to programmatically dump the values of the connected database 4GL sequences?

« Go Back

Information

 
EnvironmentProgress 9.x
OpenEdge 10.x
All Supported Operating Systems
Question/Problem Description
4GL/ABL:  How to programmatically dump the values of the connected database 4GL sequences?
How to dump the values of the sequences of a 4GL database using 4GL?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution

The following code will dump the values of all the 4GL sequences of the first connected database ( LDBNAME(1) ):

OUTPUT TO TemporaryProcedure.p.
FOR EACH _Sequence WHERE NOT _Sequence._Seq-name BEGINS "$":
    PUT UNFORMATTED
        'EXPORT '
        _Sequence._Seq-Num
        ' '
        QUOTER(_Sequence._Seq-Name)
        ' CURRENT-VALUE('
        _Sequence._Seq-Name
        ','
        LDBNAME(1)
        ').'
        SKIP.
END.
OUTPUT CLOSE.

OUTPUT TO SequenceDataDump.d.
RUN TemporaryProcedure.p.
OUTPUT CLOSE.

Workaround
Notes
Attachment 
Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.



Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful.



Characters Remaining: 255