InfoPath Dev

I believe I have found a solution to this problem.  So far, it seems to work. By default, 32-bit applications are not "large address aware" and cannot address space greater than 2 GB.  INFOPATH.EXE is no exception. To see if an application is "aware", do a  DUMPBIN /HEADERS  command on the ...

The form is published on a Windows network share and run from there. The local cache is not the problem, as new forms made to diagnose the problem have different names, so they would be copied fresh to the user's InfoPath cache. This is not Office Online; rather it's Office Professional Plus. Our guess is that there's some ...

Hilary, You are correct on all counts. Most of our users are still running Office 2010 on Windows 7, so our form is published with that in mind--InfoPath 2010 form at .NET 2.0.  All Windows 7 users are happy.  Windows 8.1 users with Office 32-bit are not.  We have the same problem no matter how the form is published:InfoPath 2010 ...

This problem is really starting to bite us now, as more of our users are installing Windows 8.1 and Office 2013 32-bit. We can create a small form and it runs just fine under Windows 8.1 and Office 2013 32-bit.  But when we try to run InfoPath Filler or InfoPath Designer on our full production form, it fails. InfoPath Designer fails with ...

We have an InfoPath form that runs fine on Windows 7, with either Office 2010 or 2013.  It also runs fine on Windows 8.n, with either Office 2010 or 2013, 64-bit. This form fails when running on a Windows 8.n system with Office 2010 or 2013, 32-bit.  The error is: InfoPath cannot open the selected form because of an error in the ...

Our group uses Windows 7 and Office 2010 to use an internally-developed InfoPath form.  The development team has recently upgraded to Office 2013 and Visual Studio 2012. The first form published cannot be run on two of our users' systems, but runs on all the others.  The error is:InfoPath cannot open the selected form because of an ...

I, too, would like to know if there's a solution.  One user of our form set his screen to the 125% setting and although the text is larger, the fields and buttons don't seem to enlarge enough to accomodate the larger text.  It certainly is a mess and I'd like to offer a suggestion for those who want bigger fonts. Paul

Patrick, I have no problem combining schema.dat and myschema.dat, and then removing mentions of myschema.dat to remove mentions of "my:" and to get rid of resulting duplicate definitions.  I assume that's what you mean by using the scalpel. But given that the form has the attribute to use additional namespaces, is ...

I do not want a "my:" namespace.  I do not want the InfoPath 2010 GUI to use the "my:" namespace when adding a new field or group.  I do not want both a schema.dat and myschema.dat file. I've changed the xsd:schema statement per the topic "Prevent InfoPath From Autogenerating a Default Namespace Prefix" ...

Can a form created with InfoPath 2013 Designer run on a system with InfoPath 2010 Filler? Paul