The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
v7 Column Bug?
Posted: 08 Jan 07 2:36 PM
|
fiogf49gjkf0d All;
Has anyone else seen the following?:
I create a grid/query in v7
Query is good in SQL and when the Grid first displays in Client
I use the column sort in the client and receive an "Invalid Column Name" Error
I go back and look at the column properties in Architect and viola - the column is aliased to the wrong table (A5.myColumn)
I look at the SQL and the column is aliased correctly. (A3.myColumn)
This seems similar to an issue resolved by SP1 in v6.2. Perhaps it is broken again?
Thanks for the info,
Carla
|
|
|
|
Re: v7 Column Bug?
Posted: 10 Jan 07 9:52 AM
|
fiogf49gjkf0d I started a project conversion yesterday, tried making a new grid, and was unable to reproduce what you are seeing with a single join query. While my example did not use any code to build out the grid, your description of the issue suggests that you passed custom query to the grid. Could you provide some more details? |
|
|
|
Re: v7 Column Bug?
Posted: 10 Jan 07 10:18 AM
|
fiogf49gjkf0d I have a five table join. I do have an onchange event (thus it fires on open) that feeds it a SQL statement. I admit to laziness on this one - I simply copied and pasted from the QBE View SQL button. It brings forth the data properly, correct recordset, placement, BindID, etc. However, the column properties display the wrong alias at Architect level.
I also have a radio group and input box filter set up. When user inputs data (or partial) and clicks which option he/she wants, it feeds new SQL into the Grid. It functions like a dream. But I still can not use the column sort without an error as the query feeds itself back in with the wrong table alias.
One thing to mention as it may have bearing on this. I did move the entire column by drag and drop in Architect. I did not change the SQL nor did the grid seem to mind.
Carla |
|
|
|
Re: v7 Column Bug?
Posted: 10 Jan 07 10:59 AM
|
fiogf49gjkf0d I have never tried letting the client create and bind columns to a custom SQL statement. I have always just passed in the custom SQL and then dynamically build out the columns based on the returned recordset fields and I have never had a problem doing it this way. |
|
|
|
Re: v7 Column Bug?
Posted: 10 Jan 07 11:27 AM
|
fiogf49gjkf0d Try sorting by another column? I suspect drag and drop from one table to another messed up something internally. Using another column to verify your code works would be a way to narrow it down to the column itself.
Does the grid have existing column definitions? If so did you purposefully re-add the column in question? You could always clear the SQL at runtime and use an exact copy of your design time SQL to repopulate the grid. That should clear up any bogus design-time entries. I would first narrow down if the column is an issue before trying to work around it. |
|
|
|