We will indeed do diagnosis, but regardless of what we find, we are not releasing a solution within the next day or so. As it sounds like you need an immediate workaround, Carl's suggestion sounds likely.

Hammer wrote on Sep 20^th, 2007 at 5:42pm:

That still fails.  I looked inside the XML export for the form, and it includes functions code that was deleted from  the GLOBAL code.  GLOBAL secrion is definitely blank.  Must be getting from another form?

In any case, I used a text editor and removed the programming section from the XML file.  It was between tags for <specs> and </specs>.  At that point, I did import again, and the file was accepted.  I then opened up the form Program Editor and imported the code that had been exported earlier. 

So, I am able to use brute force to import XML form, but still see a major bug in the Export XML area.
I am not sure I am causing other problems by manually editing the XML file.  Taking some risks here.  Problem is these files are not for me, so I don't end up with the inherent possible problems.

So steps are:
1.  Copy the form to be exported to XML
2.  Export the programming
3.  Delete all programming.  Many sections to be done, may be import a blank file will be quicker ?)
4.  Save Programming Design
5.  Export form to XML
6.  Open XML file with text editor.
7.  Locate unwanted programming between <specs> .... </specs> and delete all in between, including those tags.
8.  Save the modified XML file.
9.  Open destination application.
10.  Use Database Manager, open the destination database.
11.  Import modified XML file.
12.  Open form design, open Program Editor, import the program file that was exported earlier.
13.  Close editor and Save Layout Design.
14.  Relink Form as needed,
15.  Save Layout Design.
16.  Test and troubleshoot as needed.

Thanks for pointing out "Delete All Programming".  Don't think I recall seeing that before.  So much new stuff!  That is great for this problem.

Erika, twp of these that are failing are really BASIC menu forms.  One has four buttons, no Mass Updates, no bound elements, buttons make calls to SelectTreeItems or ExitSesame.  Another form is simpler, only has one button that calls the four-button form.  I do have other more complex forms with multi tabs, subforms, 20+ buttons.  But don't even want to start until I can get these resolved.

I did do the two noted above manually, minor things to go through.  Still avoiding the larger one since even when "programming was removed", programming was still included in the XML file.  All of these are coming from the same application. 

Here is a section where I removed code.  Has extra lines that are part of the code that should not be here:
Quote:

Looks like Type = 5.

And I also recognize this code as coming from a Mass Update Spec in the application.  That is the code for Data Dictionary.  Those first lines are comments as I was modifying the Data Dictionary code.

Don't know why it is coming in the FORM export, would expect it with the Application export, but not the form.  This looks like the specific problem, getting Mass Update Code, not necessarily the "<=" values, they just happen to be in the code.  Carl had mentioned his problem code was also associated with Mass Update.  I feel good that a solution is close at hand.

AHA!
Now I see that the MassUpdate Spec is associated with the simple Menu Form. I just went into the preview mode, opened the menu tree that is normally closed for the menu form, and looked at the Spec Manager.  Even though there are no records, there was a Mass Update spec for the Data Dictionary.

Apparently I had inserted it there at one time, months ago, and then copied it to a form with bound elements, visible Menu Tree for Mass Updates, etc.  Never removed it from original menu form.  So I knew the Mass Update was associated with another form, (one of the complex forms that I cannot import), but thought this menu form was only buttons.

So now I see, that any Saved Specs associated with the form comes over with the XML.  Now that I said that, it is so obvious.  I was thnking that the layouts and programming was exported to XML, I never though of the Spec Manger codes.  That is great, that is how it should be, everything gets exported.

Now you only need to fix the parsing of the MassUpdate programming and we are good to go!

PS, you mentions Type 5 = Mass Update.  Is there a reference of the Type value meanings available somewhere? 
.........  AHhhh, so ,  <specs> ..... </specs> are the elements associated with Spec Manager! 
This is scary, I am beginning to understand the content of the Sesame XML files.


Thanks for help and explanation.