Validating date form element

Question

Operating system and version: Win 2000
Macromedia product and version: DW8
Browser and version: IE7
Steps to reproduce:
1) Add a form
2) Name a text form element named: <%= (iCount &
".Qty") %>
3) Add a button
4) Add a date validation, or better said .. try to.
The form element is not listed in the form, form elements
NEEDS to be named
as above (<%= (iCount & ".Qty") %>)
I even tried renaming the element to say 'date', it worked, I
apply the
validation and then on the code replace 'date' for '<%=
(iCount & ".Qty")
%>', but it doesnt work.
I am using ASP/VB with MS SQL 2000
How should I solve this ? I cannot change the name of the
element and need
to validate that the element is a date (mm/dd/yyyy).
Bottom line: While the element is named <%= (iCount &
".Qty") %> I
cannot apply a validation to it, tried several extensions,
none work.
Please advice,
Alejandro

Answer 1

I want to have control over certain 'dimension type of' columns in the classic report / tabular form with APEX_ITEM.* in the sql for the report while some of the columns are from Collection with their collection column names. C001, C002 etc..
...clips
SELECT
APEX_ITEM.SELECT_LIST_FROM_LOV(35
,C035,'LOV_ANIMALS'
,'style="width:50px"','YES',NULL,NULL
,'f35_' || LPAD (seq_id, 4, '0'),NULL) animals
,to_number(c001) c001
,to_number(c002) c002
FROM apex_collections WHERE collection_name = 'SLEEPY_ANIMAL'
...clips
When there are several columns in the report, it is easier to maintain C001...columns appearance in the Report Attributes-->Column Attributes.
Oh yes, I have adapted Denes dynamic cascading lov for tabular forms which is the reason for having the "APEX_ITEM..." in the query and from some blog I read that it is very good to toss those 'dimension' type of columns to high-end numbers in the collection, so there will be space for the entry columns.
E.g. firstrow in the tabular form
c035 -- animals --> f35 --> f35_0001 (select list with lov LOV_ANIMALS)
c001 -- "what ever I have said in Column attributes"--> f01 --> f01_0001 (text area, editable column)
c002 -- "what ever I have said in Column attributes"--> f02 --> f02_0001 (text area, editable column)
So the numbering is the same for the www-form and collection columns.
Everything is ok if the columns c001 and c002 are editable e.g. 'text area' type, but if I change c001 to 'Display..' type then the order for item_id's change.
c035 -- animals --> f35 --> f35_0001
c001 -- "what ever I have said in Column attributes" (display as text (escape special chars...))
c002 -- "what ever I have said in Column attributes"--> f01 --> f01_0001
So now the collection column c002 accidentally is mapped to forms f01-column while I might assume it is f02.
rgrds Paavo