Newbie Questions

Re: Secondary Datasource Jscript Query Causing Infopath to Crash

talexander — Tue, 06 Jan 2009 17:07:12 GMT

This code is actually at the top of my file. It is only called once, and since YeastStorage is the only variable I use again (and actually I am not even using that right now), I store that globally, and discard the rest. The delete line does not need to be in there...it crashes with or without it, I just wanted to see if that would help.

I do have code that runs on context change in the master detail section, but it does not involve the connection or code above. The only time the variable I save with the code is used is when I click my query button, and the code is never used again.

Infopath may crash sometimes when you click quickly between entries, but in this case it is stable without the code mentioned, and with the code it crashes fairly quickly every time I am clicking around...I would say between 10 and 20 changes will cause it to crash.

Here is the code that runs when I change my Master/Detail selection:

function XDocument::OnContextChange(eventObj)

{

if (eventObj.Type == "ContextNode")

{

// Selection or context in the form has changed. Write your code here to respond to the changes.

if (gstrSelectedUniqueId != getSelectedUniqueId())

{

gstrSelectedUniqueId = getSelectedUniqueId();

if (null != gstrSelectedUniqueId)

if ("" == gstrSelectedUniqueId)

{

refreshDataConnection("Generation", null);

}

else

{

refreshDataConnection("Generation", new Array([/(VesselID\s)(IS\sNULL)/, "$1 = " + gstrSelectedUniqueId]));

}

}

}

}

The functions in the code get the ID of the master entry that I am on, replace NULL with that ID in the query for the "Generation" connection, and rerun the query for that connection. It is a recursive query that returns an integer that counts the interations and nothing else. The highest number of iterations it does for this specific form is 11, and the query runs extremely quickly when I run it on its own.

I will try the other syntax for accessing the secondary connection data, and see if that helps.

Re: Secondary Datasource Jscript Query Causing Infopath to Crash

Shiva — Tue, 06 Jan 2009 09:48:16 GMT

Hello,

InfoPath will crash some times, if you click on quickly on repeating master detail section. We are trying to display other detail section without showing the selected detail section. Sometime if we click twice on disable button then InfoPath form will crash.

The above code will run in on after change event of repeating node? Do you have any code for repeating section? What is the functionality of master detail section? Are you trying to connect Jscript while doing any changes in master detail section?

Re: Secondary Datasource Jscript Query Causing Infopath to Crash

Jimmy — Tue, 06 Jan 2009 04:35:04 GMT

I'm not sure why that error is happening, but I can tell you that you shouldn't be setting the selection namespaces on the secondary DOM every time a function is called. They should be set once globally and left that way.

I'm used to accessing the secondary DOM with XDocument.DataObjects["DomName"].DOM rather than XDocument.GetDOM("DomName"). I'm not sure if one's better than the other, but you could try both and see if one of them stops the error from happening.

Also, there should be no need to use the delete keyword anywhere in your code.

Please try out some of the above and see if that helps.

Secondary Datasource Jscript Query Causing Infopath to Crash

talexander — Tue, 06 Jan 2009 01:22:21 GMT

I am using this code in jscript to get info from a secondary datasource:

var YeastStoragedom = XDocument.GetDOM("YeastStorageStateID");

YeastStoragedom.setProperty("SelectionNamespaces",'xmlns:dfs = "http://schemas.microsoft.com/office/infopath/2003/dataFormSolution" xmlns:d = "http://schemas.microsoft.com/office/infopath/2003/ado/dataFields"');

var YeastStorage = YeastStoragedom.selectSingleNode("dfs:myFields/dfs:dataFields/d:VesselState/@VesselStateID").text;

delete YeastStoragedom;

The YeastStorageStateID query returns only one row, and YeastStorage is set to an integer identifier for the vessel state Yeast Storage, which happens to equal 6.

I later adjust my main connection query to return only vessels with this state ID. So far, all this code works. I can search for only this ID, or for all ID's without trouble.

The search populates a Master/Detail table in my Infopath form, and the problem comes when I try click on different entries in the master table. After clicking between several different entries, especially if I click quickly, Infopath crashes. The error signature looks like this:

AppName: infopath.exe AppVer: 11.0.8165.0 AppStamp:46365a13

ModName: mshtml.dll ModVer: 7.0.6000.16788 ModStamp:494358c0

fDebug: 0 Offset: 00216eac

Then an Application Error dialogue box pops up that says:

The instruction at "0x437e6eac" referenced memory at "0x00000000". The memory could not be "read".

If I hardwire the query in my code, excluding vessels that do not have a State ID equal to 6, and take out the code above, Infopath does not crash. However, if I keep the code in, even if I keep the query hardwired and never use the variable YeastStorage again, the program crashes. It also crashes without the "delete YeastStoragedom;" line; I just put that in to see if it would fix the problem.

What am I doing wrong?