× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Have you verified that the field you are referencing in the JSP has the 
same id in V6 as what you are inserting?

What I was suggesting was instead of trying to determine and insert the 
field id directly instead insert a replacement string that conversion will 
turn into the correct id for that field. So, where you have the following 
in the HTML_after

    inputField        : "l<%=zOrder%>_FZGH1112D1$D1SCHD6",

use something like this

    inputField        : "&{FZGH1112D1.D1SCHD6.ID}",

Then reconvert the DDS member.  Now, it might be that you need  
&{FZGH1112D1.D1SCHD6.REF} or &{FZGH1112D1.D1SCHD6} as I don't really know 
what is expected there by the Zapatech stuff.

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 12:14 PM

To
Mike Hockings/Toronto/IBM@IBMCA
cc

Subject
FW: [WDSCI-L] Migration issue from WDSC 5.1 to WDSC 6.0







Hi Mike,
Thanks for the feedback. I am referring to the book 'Understanding the IBM 
webfacing tool' (IBM press) for version 5 . If you have this book 
according to page 381, we used CODE designer , selected FZGH1112D1 record 
format, selected entry field D1SCHD6, clicked websetting tab ,selected 
insert html tab and selected 'after' tab and copied and paste the code 
from example and we customized it with our record and field. I have pasted 
below a part of the code. This worked perfectly in WDSC 5.1 but as soon as 
we open the same workspace in WDSC 6.0 it dose not work. We have followed 
the migration steps included in documentation.

   singleClick       : true,
      inputField        : "l<%=zOrder%>_FZGH1112D1$D1SCHD6",
      button            : "trigger1",

Thanks
Sanith



Hi Sanith,

To start with I would update you WDSC 6.0 to 6.0.1.  I know it is a big
hit but you will likely find it better in the long run.

Is the input field name correct?  I presume that this is inserted into the
page with Web Settings in the DDS ?  If so how do you specify the input
file for the calendar?  Is it supposed to be a name or a reference ?  If
you are inserting it with Web Settings then I'd use the right substitution
stuff to get the name or reference so that it will be correct.  There was
some changes in some of the Web Settings for v6 and they are in the
migration guide.

To get the field reference use something like this:
&{RECORD.FIELD.REF}


5.1.2 to 6.0 migration
http://www-1.ibm.com/support/docview.wss?uid=swg21212042

Web Settings
http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/com.ibm.etools.iseries.webfacing.doc/tasks/twfwsview.htm


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>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/15/2007 02:50 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'WDSCI-L@xxxxxxxxxxxx'" <WDSCI-L@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Migration issue from WDSC 5.1 to WDSC 6.0






Hi,

We are migrating from WDSC version 5.1 to WDSC version 6.0. I am using the
same workspace I use in 5.1 in version 6.0. I have followed the migration
steps mentioned in the media of WDSC 6.0. Almost all of the stuffs works
but I have a calendar utility in version 5.1 which is not working in
version 6.0.  We are using the free verson of the calendar from ZAPATECH
and mentioning their name in our code.
But when we open the same workspace of 5.1 using WDSC version 6.1 our
calendar utility stops working. We can see the calendar but it does not
load/populate the selected date from the calendar to the field.
I am also attaching the existing script in the webfacing we are using

</TD> <% lastCol=28; %>
<TD>
<button id="trigger1" style="background: transparent;border: none;">
<IMG border="0" src="/geekSquadinHome/zpcal/themes/icons/calendar2.gif">
</button>
<script type="text/javascript">//<![CDATA[
Zapatec.Calendar.setup({
firstDay : 1,
weekNumbers : true,
showOthers : true,
showsTime : false,
timeFormat : "24",\r\n step : 2,
range : [1900.01, 2999.12],
electric : false,
singleClick : true,
inputField : "l<%=zOrder%>_FZGH1112D1$D1SCHD6",
button : "trigger1",
ifFormat : "%m/%d/%y",
daFormat : "%m/%d/%y",
align : "Br"
});
//]]></script>

I would really appreciate any king of help regarding this matter. Please
let me know if any further information is needed. I am new with WDSC.

Thanks
Sanith

--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.