Search results

You might want to post just a tiny little bit more code as an actual working example. Maybe use the "customer" table in the sports database?

No. Unfortunately, there is no such VST.

I suggest that you reach out to @peterjudge at Consultingwerk. Peter and his team have the experience that you are looking for.

"for Audit Trail Purpose" suggests that you have a requirement for an audit trail. Triggers are not an appropriate mechanism for an audit trail as there are many ways to defeat them. OpenEdge Auditing is the appropriate tool to implement an audit trail. It's also free (from a licensing...

We create our prolibs on Linux and deploy them on Windows. The prolib format is portable across platforms. R-code compiled on Linux will run on Windows (assuming the same OE version). Windows r-code that uses GUI features will not run on Linux. In both cases references to external DLL calls...

No. VALUE() is a keyword associated with statements that allow filenames and paths to be hard coded. VALUE() is basically saying “it’s not hard coded this time”. File names and paths need to be handled specially in this manner because the default syntax allows you to hard code them directly...

What part of "there is something sending a large number of requests to Qxtend" fails to qualify as the RCA? There is a lot of activity. Lots of activity means app servers are busy. If you don't like that the app servers are busy you can: 1) start more of them (if your systems have the...

The Pro2 documentation is online here: https://docs.progress.com/category/pro2

The first problem that you will have is that it is not available for version 9.

All of the Progress documentation is online: https://docs.progress.com/category/openedge-archives

OpenEdge 10 certainly has lots of support for XML. OE10 is 20 years old now and hasn't been a "current" release for a long, long time. I'm too lazy to look it up but I don't think that OE10 has much if any explicit JSON support. OTOH, JSON output is pretty trivial to create. Parsing JSON input...

What version of Progress are you using? If your Progress release is older than XML (or JSON) then, no, it won’t be supported. If your Progress release is reasonably modern then, yes, it is supported.

Aside from the Windows performance considerations... a more fundamental reason to not overwrite the old backup is that, as soon as you start the new backup the old one that you are overwriting is unusable. And if something goes wrong before the new backup completes you are without a valid...

IOW - target 12.8 for any migration.

It sounds like you have a fairly complex setup. You might want to engage an experienced consultant rather than try to work it out in an online forum ;) Incidentally, and apropos of nothing - I'm going to be in Europe for the next couple of weeks.

That's too bad. Is the vendor at least still providing support and bug fixes and willing to move you to a modern OE release? To use the horizontal table partitioning approach someone will need to write some code and either compile it onsite or provide r-code. If you have an onsite compiler...

Do have access to the source code?

Just be aware that that technique requires the horizontal table partitioning add-on and that could create problems with older code if the old code uses RECID in inappropriate ways (almost all usage of RECID is inappropriate).

The space in a block freed by deleting records will be reused as new records are added (and if old records grow). For index blocks you need to run idxcompact to reclaim the space. (That can be done online.) There are many ways to dump and load. Some methods can greatly reduce the required...

The original post says: True, the concern is the speed of those tasks and there are ways to improve that stuff which do not involve purging data but I actually found this rationale to be a refreshingly solid set of reasons for wanting to purge. The more typical reasons usually boil down to...