Hi Team,

Thanks for your help so far. I have a searchable drop-down in a maintain data addition form. Done that using Ajax. When the user fills all the textboxes in the form and clicks add . The screen goes blank and i get the scary "eda nodata" message. When i disabled the .js file embedded in the maintain screen. The data addition form works as expected.
Following is a snippet of ajax code used.

 


var xmlHttp = false;

try {
  xmlHttp = new ActiveXObject("Msxml2.XMLHTTP");
} catch (e) {
  try {
    xmlHttp = new ActiveXObject("Microsoft.XMLHTTP");
  } catch (e2) {
    xmlHttp = false;
  }
}
if (!xmlHttp && typeof XMLHttpRequest != 'undefined') {
  xmlHttp = new XMLHttpRequest();
}

function CallServer(searchString)
{
	// Build the URL to connect to
	var procName = '';
	procName = 'app/searchfundid.fex';
var searchStrings = searchString.toUpperCase();
	var rand = new Date().getTime();
	var url = "WFServlet?IBIMR_domain=domevstr/domevstr.htm&IBIMR_action=MR_RUN_FEX&IBIMR_sub_action=MR_STD_REPORT&IBIMR_fex=" + procName + "&IBIF_ex=" + procName + "&IBIMR_flags=&IBIMR_folder=#evestmentrep&IBIMR_random=" + rand + "&IBIMR_user=a488795&IBIMR_drill=RUNNID&Submit=Submit&VALUE=" + escape(searchStrings) ;

	 // Open a connection to the server
	 xmlHttp.open("GET", url, true);
	// Setup a function for the server to run when it's done
   	xmlHttp.onreadystatechange = PopulateItems;
	 // Send the request
	 xmlHttp.send(null);
}

function PopulateItems()
{
    if (xmlHttp.readyState == 4 && xmlHttp.status == 200)
    {
        var responseXML = xmlHttp.responseXML;
        var trs = responseXML.getElementsByTagName("tr");
		var FUNDDL = null;
        var textIndex=1;
		var valueIndex=0;

		    FUNDDL = document.getElementById('FUNDDL');
			textIndex = 0;
			valueIndex = 1;
			FUNDDL.options.length = 0;
            for (r = 0; r < trs.length; r++)
{
            var tds = trs[r].getElementsByTagName("td");
            optn = document.createElement("OPTION");
            optn.text = tds[textIndex].firstChild.nodeValue;
            optn.value = tds[valueIndex].firstChild.nodeValue;
            FUNDDL.options.add(optn);
               }
			   if ((document.getElementById('EditBox5').value != '') && (FUNDDL.style.visibility == 'visible'))
			 { FUNDDL.selectedIndex = 0;
			 }

}
}


 function text_onchange()
{

	   var FUNDDL = document.getElementById('FUNDDL');

		var EditBox5 = document.getElementById("EditBox5");
		if (FUNDDL.value != '')
        {
		EditBox5.value = '';
		EditBox5.value +=  FUNDDL.value ;
	}

} 

This message has been edited. Last edited by: Kerry,

What .js are you disabling ?

Did you know that IBI supplies a js file for xmlhttp ?, its called ibihttpxml.js.

The IB .js files for ajax also use the variable xmlHttp. They may be tripping over each other. Try renaming that variable as the first step.

Hi Alan/Waz ,

Thank you so much for your replies.

Waz - I deleted the ajax code js file i have embedded in the form.

Alan - I have changed the variable name to xmlHttps . Still i get the same eda no data error. I raised a case with IBI 81072519 i got the following response

"Maintain is a persistent environment, you cannot have ajax script embedded in
the form unless you are do a winform show exit. This explain why you are
getting eda no data screen.
"

Any suggestions most welcome

It seems that the statement that you cannot use Ajax with a persistant Maintain application was premature.

We have seen examples where using it with a persistant application works just fine. I know there is a case open for this issue. If you can upload a SMALL reproduction with repro steps, that would be the best thing for us to debug.

Thank you!
Mark Derwin

Hi Mark,

Thank you so much for your reply. If you have access to the IBI case 81072519 , i request you to go through the code and snapshots attached to it. Hmm i dont think the whole code can be loaded in the forum. Will upload the code in the next post.

Your help is much appreciated.

Aravindan

Arvindia, Mark works for IBI, and IS the Maintain Wizard.

No need to upload code here is you don't want.

I also think that this can be done. As I think I've done it before, but it was a very long time ago.

Hi Mark/Waz

Could you give any hint or suggestion in this regard. I have hit a mini roadblock here , i have implemented this code in Webfocus , but i dont understand why maintain is causing incompatibility issue.

Mark,

We also talked to our customer relations contact Brian Joy regarding this case and suggested your name since you are the maintain pro.

Thank you all for your help

Aravindan

Are you able to generate a sample maintain app that has this issue, and send it to me ?