|
I don't really know then. Have you checked the Zapatec site for help? http://www.zapatec.com/website/forums/viewtopic.php?p=2814&sid=fe6be865182db33c6d98c4fbe222d159 Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx voice 905 413 3199 Sanith Ray <sanithray@xxxxxxxxxxxxxx> 02/16/2007 03:58 PM To Mike Hockings/Toronto/IBM@IBMCA cc Subject RE: [WDSCI-L] FW: FW: Migration issue from WDSC 5.1 to WDSC 6.0 Hi Mike, I opened FZGH11112D1 with code designer and went to 'insert html' then 'after' tab changed to inputField : "&{FZGH1112D1.D1SCHD6.ID}", Then I converted DDS. The calendar still doesn't work ( doesn't populate to the field). I am also attaching the jsp file after conversion. Thanks Sanith -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Hockings Sent: Friday, February 16, 2007 2:28 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] FW: FW: Migration issue from WDSC 5.1 to WDSC 6.0 No, in the JSP I would expect to see something like: inputField : "l<%=zOrder%>_FZGH1112D1$D1SCHD6", or even maybe inputField : "document.SCREEN.l<%=zOrder%>_FZGH1112D1$D1SCHD6", I don't really know exactly what the js you have is expecting. But in your DDS source you would have something like inputField : "&{FZGH1112D1.D1SCHD6.ID}", Then once you get it working you know it will convert to the right thing each time. Web Settings http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/com.ibm.etools.iseries.webfacing.doc/tasks/twfwsview.htm Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx voice 905 413 3199
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.