Sounds like an XSL issue. I'm not aware of InfoPath making use of keys
(though they might behind the scenes).
Check your XSL files for any instance of "xsl:key" or "key("

Signature
Greg Collins
Microsoft MVP
Visit Braintrove at http://www.braintrove.com
Visit InfoPathDev at http://www.infopathdev.com
Hello,
Just to be on the safe side I'd expand on what Greg says and just search for
any instance of 'Current_Goals_23' in all the files within the XSN file. It
could be an issue with the myschema.xsd as well. Identity issues might be a
schema-related issue.
Gavin.
> Sounds like an XSL issue. I'm not aware of InfoPath making use of keys
> (though they might behind the scenes).
>
> Check your XSL files for any instance of "xsl:key" or "key("
ALAS - 25 Feb 2008 14:19 GMT
Thanks! I found and removed the reference from the xsl files as well.
Unfortunately, the xsn and xsl files contained additional references to
previously deleted controls. I am not sure why the references remained in the
xsn and xsl files, but no longer appeared in the template. After removing all
bogus references, I was able to open the template and continue to work
without losing and data.
Thanks again!
Angela
Greg Collins - 26 Feb 2008 01:02 GMT
Every once in a while, you get random junk left over in your files. A prime
example is the unbound control entries in the manifest.xsf file that remain
after deleting buttons from your view. These don't harm anything, but it
would be nice if they were properly cleaned up.

Signature
Greg Collins
Microsoft MVP
Visit Braintrove at http://www.braintrove.com
Visit InfoPathDev at http://www.infopathdev.com