When I use the code generator to create the html, the tool does not allow me to specify what type the control is. This mean I have to go in and clean up the generated code after it is done generating the HTML - that sucks! The generator just needs to be fixed to know about the newer AJAX controls, than the problem would go away along with my annoying comments!<s>

--hm

You need to specify the type on the control and then it works as you would expect.

+++ Rick ---

I did not see anything in the instruction about the generator tools partly working. <s>

Am I missing something here or should your tools be inconsistent with regards DATE VS. DATETIME fields and the AJAX class names it generates?

The generator tool was run within the v5.4 environment and produced inconsistent results! This was NOT and issue of my needing to update the class names manually to existing code.

Please test running the generator on a table that has both a date and datetime field defined. The result is very consistent - INCONSISTENT HANDLING OF DATE VS. DATETIME FIELDS.

This is a BUG or one hell of a new feature! <s>

--hm

Please read the update instructions for Web Connection 5.4. The AJAX classes have all been renamed.

+++ Rick ---

Version WC 5.4

Selected... Web Connection > Tools > Table and Index and HTML Generator

with my target table open that has both datetime and date fields

selected to generate Webform Edit Form, then cut and pasted the generated html into the VS wcsx form I was creating.

Pointed my browser at hte new file after saving and WC returned an error page that reads:

Parsing of the page UserEntry.wcsx failed.
Couldn't create control: txtExpireson [wwwebdatepicker].

Error: Class definition WWWEBDATEPICKER is not found.

I have since traced the problem to the the generator producing incompatible code. The html string reads:

<ww:wwWebDatePicker runat="server" id="txtExpireson" ControlSource="this.Page.oUsers.oData.Expireson" />

Which shows the error if you look close enough... the generator tool is using the old syntax from prior to 5.4, namely the control is now called wwDatePicker with the "Web" excluded.

Because the generated page had four date fileds and only one was causing the problem, it was a bit of a puzzle. As it turns out the difference is the broken syntax was generated from a "DATE" field whereas all the ones that worked correctly were generated from a "DATETIME" field.

--Harvey

---