index | search | no replies | posting guidelines | help

login | register

Index » Products » ASP Report Wizard v2

search this forum:

:: Column Name Resolution :: (6) Post a New Message | Post a Reply
Nov 30 2004, 7:53 AM	Column Name Resolution Post a Reply
Darin from: Conway, AR	The wizard seems to be having trouble with columns in views that are named similarly.  In one of our views, there are columns named [Conference IEP Date Due] and [Conference IEP Date].  The wizard loses the word 'Due' from the first column, and displays the [Conference IEP Date] column twice with the same data. Any ideas and/or fixes for this?
Nov 30 2004, 9:02 AM	Re: Column Name Resolution Post a Reply
ghost from: Washington, DC	What version of the report wizard are you using? I think this bug had been fixed a few versions ago. ------------------------- Ghost
Nov 30 2004, 9:08 AM	Re: Column Name Resolution Post a Reply
Darin from: Conway, AR	Ok, I'll update and retry. Thanks.
Nov 30 2004, 1:27 PM	Re: Column Name Resolution Post a Reply
rcasey@octane8.com from: Birmingham, AL	I wanted to post on something similar to this too.  To begin, I have the penultimate build of the report wizard. When I do a join between two tables, and select two fields that have the same name, I am unable to sort and filter the result set from the report interface.   I had two columns with the name, 'name'.  I did the column renaming feature in the wizard, so that the first column 'name' was 'Severity', and the second column 'name' was 'Customer Name'. When I would try to filter Customer Name, your software would try to filter the Severity.  If I would then try to filter Severity, then it would just fail. See if you can reporduce this...  if not, I'll make something public.
Nov 30 2004, 1:39 PM	Re: Column Name Resolution Post a Reply
Darin from: Conway, AR	You may be able to assign an alias to the conflicting column names inside of your stored procedure or view or whatnot that will help to take the decision out of the report wizards hands.
Nov 30 2004, 2:06 PM	Re: Column Name Resolution Post a Reply
rcasey@octane8.com from: Birmingham, AL	That's a fine workaround.  Thanks.
Pages: (1)   [1]

search this forum: