Re: new CASE keyword conflicts with old table VPPRO column name

One of the main problems is that the select stmts are coded in the view point dll's. So modifying the select is out of the question. We had a similar problem when upgarding from 7.14 to 7.30 Informix eventually gave us some updated vp dll's which helped and we chanegd the 'case' column to csae. ( a delightful bodge - doen at informix's request ). On a more serious note the only people who would generally consider vp are corporations that received vp along with a new era release prior to version 3. With the updated dll's informix gave us we where able to use view point but the window painter still kept failing on the prepare statement. I think the window painter also has the SQL hard coded and informix didn't seem to want to send us updated dll's for one of there dying products. Jo Jonathan Leffler wrote: > > Michele Iacobellis wrote: > > > > Hi all. > > > > I'm porting an old application from 7.13 to IDS 7.31. In this application > > reports are generated via ViewPointPro. One of the tables used by > > ViewPointPro (syscolformats) has a column whose name (case) conflicts with > > the keyword case present in IDS 7.31 SQL syntax. So, when I run a report, > > the statement: > > > > SELECT colname, priority, typeface, fontsize, fontstyle, fontcolor, > > formatmask, align, case, ruletype, checktext FROM > > "informix".syscolformats WHERE owner='informix' AND> > tabname='xxxxxxxxxx' > > ORDER BY colname, priority > > > > gives -201 syntax error. > > > > Before mangling the binary of ViewPointPro to change this unfortunate (and > > unwise, maybe) column name, I would like to know if there is another > > workaround less brute-force oriented. > > Hmmm...interesting problem. I don't know to what extent the designers > of VPPro can be faulted for not be prescient. I fear it was released > after the SQL-92 standard was finalized, so the prescience required > was not huge... > > Howver, there is one simple way to work around the problem, and > several more dubious alternatives: > > SELECT ..., F.Case, ... FROM "informix".syscolformats F WHERE ...> > SELECT CASE AS CASE FROM ...> > Set DBDELIMITER environment variable (woe unto you if you try this, > but the code you showed is written so that it is safe), and write: > > SELECT "case" FROM ... > > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN > #include <disclaimer.h>

Joseph Cooper <joseph.cooper@lineone.net> wrote in message news:7pjuul$35o$1@news.xmission.com... > Informix eventually gave us some updated vp dll's which helped and we > chanegd the 'case' column to csae. ( a delightful bodge - doen at > informix's request ). Nice, I'm going to ask for these dll's to my local Informix support. Do you know if this is the only one issue of this kind in the compatibility between VpPro and IDS 7.3x? Michele