I seem to have answered my own question! I can still work with the 'lower case' field names while I am in the ReportDesigner running off the TestCursor - but as soon as I run against my live database then the attribute can't be found message appears on the report.
I previously generated some reports (about Nov '08 I think) and this conversion of field names to lower case in the editor was not happening then. It appears to happen on loading the rfxml file as the changed data appears in the xml editor if you go to that tab immediately after loading the file. At the same time the conversion of ' to ' occurs. Interestingly when I use my original rfxml file against my 'live' database programatically rather than in the ReportDesigner it works perfectly, but leaves the upper/lower case and the ' punctuation unaltered. I'd really like to use the Visual Editor for my reports, but the way it changes field names makes this impossible currently. Where do we go from here? Rodgy ----- Original Message ----- From: "Roger Lovelock" <[email protected]> To: "Dabo Users list" <[email protected]> Sent: Thursday, February 26, 2009 12:21 PM Subject: Re: [dabo-users] Report Designer Problem > Have actually got a test cursor working OK now - but am seeing some > unusual behaviour - I initially set up the test cursor in another editor - > all worked fine when I loaded it into ReportDesigner and looked at > preview. When I save the rfxml file from ReportDesigner all the uppercase > in the TestCursor section gets converted to lowercase ie MyFieldName > becomes myfieldname etc etc. This then extends to the visual designer when > trying to add fields etc. Python is case sensitive so.... > Is this a problem? > > Rodgy > ----- Original Message ----- > From: "Paul McNett" <[email protected]> > To: "Dabo Users list" <[email protected]> > Sent: Thursday, February 26, 2009 10:24 AM > Subject: Re: [dabo-users] Report Designer Problem > > >> Paul McNett wrote: >>> Roger Lovelock wrote: >>>> Since I can't use the ReportDesigner without a TestCursor does that >>>> mean I >>>> should try hand coding the rfxml file and test it with my 'live' >>>> database (I >>>> have no problem with this concept - its just that its not the way I >>>> assumed >>>> report design should be done). Please correct me if I am wrong, but my >>>> impression is that the ReportDesigner only knows what fields are >>>> available >>>> from the test cursor as no link to a Bizobj is available from the >>>> ReportDesigner. Am I right? >>> >>> ReportDesigner wants the TestCursor, correct. >> >> ...but you can still use the ReportDesigner with no TestCursor (just fill >> in the >> field expr's manually). >> >> Paul >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/5402e4087dd64535bc26b9efb9a1c...@roger
