I wonder if anyone else is aware of the implications of some of the changes
to the SDO for 9.1D. Until this release, it was possible to use the SDO with
an Open Client connection, in fact it was even encouraged with the inclusion
of example Visual Basic code to do just that. With the release of 9.1D, the
structure of the SDO has changed, and as a result many of the procedures that
were exposed by Proxygen are no longer availalable. Unfortunately this includes
setQueryWhere, getQueryWhere, setQuerySort etc etc. The result is to render
the SDO virtually useless through an Open Client connection.
Has anyone else gone down this road and have any suggestions etc. We have invested
a significant amount of time developing a system using the SDO through an OPen
Client connection, only to come across this problem and a solution from Progress
does not seem to be forthcoming.
After speaking to someone at Progress UK I have an answer to the problem incase
anyone else reads it. The problem occurred because the definitions of the functions
and procedures in queryext.p are not included in qryprto.i. To solve this simply
run the ProtoGen tools on src/adm2/queryext.i and paste the include file it
generates onto the bottom of src/adm2/qryprto.i, then recompile your SDO's
and regenerate your proxy.
Hopefully this will be sorted in the next patch (if it has not already been).
"Nick Finch" wrote:
>
>I wonder if anyone else is aware of the implications of some of the changes
>to the SDO for 9.1D. Until this release, it was possible to use the SDO
>with
>an Open Client connection, in fact it was even encouraged with the inclusion
>of example Visual Basic code to do just that. With the release of 9.1D,
>the
>structure of the SDO has changed, and as a result many of the procedures
>that
>were exposed by Proxygen are no longer availalable. Unfortunately this
>includes
>setQueryWhere, getQueryWhere, setQuerySort etc etc. The result is to render
>the SDO virtually useless through an Open Client connection.
>
>Has anyone else gone down this road and have any suggestions etc. We have
>invested
>a significant amount of time developing a system using the SDO through
>an OPen
>Client connection, only to come across this problem and a solution from
>Progress
>does not seem to be forthcoming.