You do not mention what the error is you are seeing or why you think it is the ‘Convert to Syntax’ is causing the issue?
You say a runtime error, could there be a retrieve where the returned rowcount is not tested and then e.g. a GetItem is done and no row is found?
I have taken many PB classes and worked in numerous large corporations with extraordinary developers and have never seen the must save to ‘Graphics mode’. I am not saying it is not correct, simply sharing that is the first time I have seen that. Also, the link posted is from 2005.
Be this the case(graphics mode save), I wonder how a Stored Procedure behind a dataobject if/would impact this?
Thoughts on using Convert to Syntax:
- It could be as simple as style. An app with 4000 objects, that tells me there must have been many, many developers over the years and I am sure each and everyone had their own ideas on how to use Powerbuilder. That is not directed at anyone just what I have seen in many applications.
- Is there a pattern? e.g., The objects which use the graphic mode is it very basic SQL, Select From Where.
- The dataobjects Convert to Syntax, the SQL does it use e.g., Outer joins, Unions or other SQL syntax where building in graphic mode would be time consuming or not possible?
I cannot remember the last time, I used or saw graphic mode used. For the most part, the SQL I put behind dataobjects is very complex. I build outside the object, test, check the where clause is properly structured, test, then cut and paste into the dataobject.
I would prefer a Stored Procedure but am a contractor and have to adhere to the site standards and SP's are not always used.
4000 Objects, I can’t imagine regression testing and signoff must be time consuming. Also, this leaves so much room for error, duplication and trying to figure out where an issue is and how to find it. It also makes me wonder if some developers created basically the same object over and over instead of modifying a Where clause.
