https://www.infopathdev.com:443/forums/45.aspxenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/125571.aspxMon, 23 Sep 2024 14:59:28 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125571Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/125571.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&PostID=125571It has been many years since I've looked at VBScript for InfoPath... but I'm wondering what happens if you leave that line of code that is resetting the gobjXDocument commented out? I'm curious why that variable is being set and then reset.https://www.infopathdev.com:443/forums/thread/125570.aspxMon, 23 Sep 2024 03:32:42 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125570thegoat770https://www.infopathdev.com:443/forums/thread/125570.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&PostID=125570I am in a team in a large organisation that supports a number of InfoPath forms. We are having a strange problem with one form in particular since a few weeks ago. We have narrowed it down to the fact that a recent Microsoft Office update that our IT group rolled out, specifically version/update 2402. Basically those PC's that don't have the update can open this form ok, but for those that have the update installed, InfoPath will open briefly, but then close out before the form opens. I admit I'm not an InfoPath expert, but I do know that form references a number of VB scripts. As such, we have narrowed down the issue to one line of code (in a large file of other functions). Specially, it seems be when it does this - "set gobjXDocument = window.external.window.XDocument". The two lines that precede this are "window.returnValue = 1" and "set gobjXDocument = window.dialogArguments" When the line of code I mentioned s commented out, the form opens, but when it's not, we experience what I mentioned above where InfoPath will open, but then close without opening the form. Could anyone assist? Thanks in advance