Code

Re: Error Message: Undeclared Namespace

dlgross — Tue, 07 Oct 2008 14:35:34 GMT

You were correct, thanks

Re: Error Message: Undeclared Namespace

Hilary Stoupa — Tue, 07 Oct 2008 14:27:35 GMT

My first guess is that the Alert method should be capitalized.....

Re: Error Message: Undeclared Namespace

dlgross — Tue, 07 Oct 2008 14:09:52 GMT

Hilary, thanks for the tip. You were correct, I have added the namespace definition to the top of the js file and the undeclared namespace error is gone, but now I am getting an "Object doesn't support this property or method error" on the following line:

XDocument.UI.alert(e.description);

Any idea what could be wrong with this? i am using IP 2007 and saving as 2003.

TIA
Dean

Re: Error Message: Undeclared Namespace

Hilary Stoupa — Fri, 03 Oct 2008 18:17:57 GMT

Hi:

When we add an event to an InfoPath form, when working with jscript, IP will add the namespace definition at the top of the .js file. For example:

XDocument.DOM.setProperty("SelectionNamespaces", 'xmlns:my="http://schemas.microsoft.com/office/infopath/2003/myXSD/2008-10-03T18:12:27"');

Since you are getting an undeclared namespace error, I'm wondering if that was somehow erased or removed from you .js file. Could you check and see?

Error Message: Undeclared Namespace

dlgross — Fri, 03 Oct 2008 17:33:24 GMT

I have the following code and I get an Reference to Undeclared Namespace prefix: 'my' error. I have looked through this forum and can not figure out my mistake. Could someone please tell me what I am doing wrong?

function CTRL102_5::OnClick(eventObj)
{
// Write your code here
var jobNumber = XDocument.DOM.selectSingleNode("/my:myFields/my:JobNumber").text;
try
{
var cn = new ActiveXObject("ADODB.Connection");
var sqlSP ="EXEC dbo.uspJobAndContract ' " + jobNumber;

cn.ConnectionString=XDocument.DataObjects("JobData").QueryAdapter.Connection;
cn.ConnectionTimeout=XDocument.DataObjects("JobData").QueryAdapter.Timeout;

cn.Open();
cn.Execute(sqlSP);
cn.Close();

eventObj.ReturnStatus=true;
}

catch(e)
{
XDocument.UI.alert(e.description);
eventObj.ReturnStatus = false;
}
}