No, I was only listing JSON as one of many ways to pass data. In order to make a recommendation of the preferable way to exchange the data, I would have to know more about your actual requirements.
I might note that I tend to frown on passing temp-tables regardless. Better to encapsulate them...
For starters, I would recommend that you *not* do big complicated things in constructors. If they fail, you are left with a class that doesn't exist and the error handling is consequently more complicated. Better to initialize the class with a minimal constructor and then use an Initialize...
It is very unclear what you are trying to do or expecting to happen. As Stefan said the USING statement has no function than to allow the use of an unqualified class name in the remaining body of the class. I.e., being able to reference just "base" instead of "ProcedureLibraries.base"...
There are many different answers, depending. Is the time you have a string or a date-time datatype or what.
Are you looking for seconds since midnight?
This is a plus for other uses of substitute as well, e.g., some kind of slice and dice where one could assemble pieces, but it would require additional logic to detect and handle unknown values.
More info would be useful as usual. What version of Progress. What license model? Do you have replication? If not, why not? Might it be a solution to run the read-only users on the replicate?
If you are refreshing these temp-tables every 5 minutes to have current data for reporting, then...
If you have a top level procedure which is not connected to the DB ... and I am not particularly sympathetic that it is sensible to be so stingy with licenses ... then the usual thing is to connect to the DB and transfer control to a subprocedure since it is only in that subprocedure that the DB...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.