Search results

So you need to not do that and only create what you need when you need it. If you want a temp-table with multiple records, you need to create the temp-table once and then create multiple records in that temp-table.

You are creating the dynamic buffer, query and temp-table per index field of the unique index on table 'test'. So you are: not getting what you need leaking memory since you are repeatedly creating dynamic objects over each other

Since JSON is not a line based format, you cannot simply append like with the output statement, so you need to: read-json file into temp-table create temp-table records write-json temp-table to file

You may also want to have a look at the quoter function: Progress Documentation

-tok is a client startup parameter, so it needs to be on the command line directly or indirectly (-pf) of whatever is starting your ABL session.

Which Java version are you using? You need to be using an 11.0.x version.

Or just increase the value of startup parameter -tok, the default value for any current version of Progress is 3000 - for older versions see Progress KB - What is -tok parameter ?

r-code caching is a startup parameter: -q to clear the cache from within the ABL: current-language = current-language to clear the cache from outside: asbman -trimagents

Create a delete trigger. Which has an interesting oddity in the notes:

Repeatedly dating a substituted string with an assumed session DMY format is asking for trouble. Use the date function with three integer inputs for month, day and year, it will work regardless of the session settings:

The tool is Progress Data Administration. I'm fairly sure that move is just a poorly chosen name, since it just creates insert statements for all your data and does not remove your original data...

Assuming you are not a spambot, what are you using to send mail?

Yes, see documentation: load get-key-value put-key-value

What does your software do? How can you prove that your software works correctly? Are there parts of this proof that can be automated?

In an ideal world in which bugs do not exist, you are correct. My priorities in your case would be: source control automated builds (pct) automated testing of these builds continuous integration Modern tooling helps for all of the above. When introducing a new version of anything in your...

A personalized folder / propath sounds like you are not using version control? Local dev = 'personal'. Your 'recent file list' is the thing which I continuously undo from version control if I accidentally use the procedure editor. Unfortunately you cannot stack INI files: prowin -inifile...

Can you give an example of a more personalized thing?

Why? source: https://www.ietf.org/rfc/rfc4627.txt

Use the TITLE attribute, when it has the unknown value, the browse does not have a title.

Just one caveat which had me scratching my head for a while, the batch file also sets the DLC environment variable, which allowed me to use this when building with Ant / pct.