Search results

1. please put code inside [ code ] tags to make it legible 2. when you have a problem and would like others to help you with it, it helps if you reduce the problem to the smallest version of the problem. Showing how you assign NINE fields with all sorts of crap does not help. What you need is...

Not that I can share. I can share that we started by reducing an xlsx to a bare minimum (there is a lot of fluff in an empty worksheet) and then building it up with our content. It's a lot more fun than reading through pages and pages of specifications.

We use option 3 Create an xlsx file (is multiple xml files created using sax-writer, which are then zipped as xlsx) - fetching simple data (1 table), creating report and creating excel file takes less than 1 second (640 records, approx 20 columns)

If your backend service can use .Net and if it can create an ABL window and if you can hoist this in a .Net window, then you may be able to use the CopyFromScreen method.

If you view the documentation on the RequestBuilder you can see what the Put method needs: OpenEdge.Net.HTTP.RequestBuilder Put (character, Object) OpenEdge.Net.HTTP.RequestBuilder Put (URI, Object) OpenEdge.Net.HTTP.RequestBuilder Put (URI, Object, character) So you always need to...

/* why break-by ? - probably for the LAST( ), but won't hurt, only a small table for 1 customer*/ Let's just assume that this is not entirely true. :D

The question title: But, using your example and manually creating the child records based on the extent, may be easier but also more error prone, than digging into how JsonObject and JsonArray work.

Of course it fails, that's why you need to disect the json yourself using JsonObject and JsonArray - look these classes up on docs.progress.com google site:docs.progress.com JsonObject google site:docs.progress.com JsonArray

Yes, although with your structure you will need to disect the json yourself using JsonObject and JsonArray.

That's not really your calculator though, is it James ;-). My calculator returns an error:

Working as documented Progress Documentation

If you just need to know which tables are hit, to get insight into the black box your application may be, you can monitor this using _TableStat or _UserTableStat To not reinvent the wheel, you could look at - the free version of - ProTop.

Those are all possible approaches, you can also use the outcome of this as a default that the user can change if needed. Upon reading data, if you get an exceptionally high number of errors due to data type mismatches, you could retry.

What ideas do you have so far?

You can compare them, you just cannot use them in a query. So I think you are going to need to rethink what you are trying to achieve.

Both a longchar and a clob are large objects, so this is not going to work.

Why could you not write:

Deserialize your json to a temp-table and use that, this should get you started: def var lcjson as longchar no-undo. lcjson = '~{"Customer": [ ~{ "cust-num": 121, "name": "Jack", "state": "Texas", "city": "Houston" } ]}'. def var ht as handle no-undo. def var hb as handle...

Your trigger file: { deletetrigger.i customer } the include file // deletetrigger.i procedure trigger for delete of {1}: run scankey ( ( buffer {1}:handle ) ). Or if you have a strong dislike for ordered parameters: { deletetrigger.i &table = customer } with // deletetrigger.i...

You will need to transform the static buffer to a buffer handle. Static means at compile time. So you will need a stub program per table that contains the table name, you already have this for your delete trigger procedure. Maybe the following helps: // this is the delete trigger, it contains...