Once again, I have an XML file that is not importing.

Somehow, a form was lost in DSR.  Had four tabs, one with a subform.  All the other tabs with elements, programming, etc are gone.  Trying to locate a backup copy, but it looks like customer does overwrite each night vs. daily copies....aaargh!  That will now change.

Have located a copy a few weeks old and did an XML export of FormName1, saved as FromName2.xml.
Opened DSR, Manage Database and did Import XML of FormName2.  But this imported form does not show up.  Data Source in XML is correct for existing DSR.  Imported a second time, same result, see hourglass, and flashing, etc. when done, no new form is in DSR.

The fields are in the database, but not bound to any elements because they are all missing with the missing tab pages.  The XML does include Imort and MassUpdate specs for elements that do not exist, do they need to be removed to allow import to the database?

Bob,

XML import usually works fine and elements do not usually vanish from forms, so we'll have to look at your specific case. Support will likely get in touch with you on Monday and request your files.

This is very unusual that no solution is available yet.  Problem has been confirmed.   I appears that XML imports can be done OK at the top level, but importing at lower levels is a problem.  Is anyone else having this trouble?  This application is using subforms nested five and six levels deep.

I know they are working on it.  I was just on the phone with them before I updated the posting. 

But I posted it here to alert others about the possible problem.  I would discourage users from doing XML imports/exports with subforms until this problem is understood and resolved. My client is now concerned that Sesame may not be able to handle multiple subforms, but I have assured them that Lantica will come up with a fix.

At this point, our project is essentially on hold until we know what it will take to fix the design.  Am afraid that all forms may need to be manually recreated again, the time and cost to do that are scary without the XML tools.

Here is my best recollection of this application history.

This started with the release of version 2.0.  The new import/export XML ability led to the creation of a "common template".  The common template was designed and tested as a single level form and kept in a master application of tools. 

A new application for this client was started by doing XML imports of the "common template" into about 10 databases in the single application.  Then each form was modified as needed adding/deletion elements, programming, etc..  Then forms were linked with relational links in nested subforms about 6 or 7 levels deep.  Additional programming added to help control opening as standalone or as subforms.  After that, no more forms were imported.  Then recently, natural links were created to replace the relational links.  Ascii file records were imported, and reparenting was accomplished, worked fine.  We have not been having any reconcile problems that I am aware of.

At one point in the process, problems with colors started occuring, and Lantica said the problem was a result of XML problems, and that would be corrected in the next r

elease.  I think the next release was about 2.03 or 2.04.  But the solution at that time for the existing forms would be to totally replace the form if it displayed the color problem. 

The current issue came about when all elements on a subform, four levels deep,  disappeared (still no idea of how that could happened).  That form was one that had been rebuilt from scratch earlier (I think).  So it was decided to get a backup and export the form using XML and import it into the current application to replace the existing one that was missing all of the elements.  So, the export happened, and the import process was done, but no report was imported.  Did some editing to the XML files to remove specs and events, etc. with no change.  Cannot import this form back into this database.

But, we are still seeing random color problems, so the fix might be in for XML imports after 2.03, but those imported before the fix, may still have some underlying problems?  We have also had some random GDI errors that are not able to be produced on demand or predicted. 

So, is there something wrong in the whole application?  Only in this subform?  Could the whole application be exported and imported as a new application, replacing the existing one?  Or can that not be done because we would just be copying defective forms?  Do I need to eliminate the nested subforms and redesign into flatfile structure using XLUs vs. natural linked subforms? 

Re your efforts to reestablish links, I don''t think I need that.  The one element that remained on the form was the link to the child subform..  All the other elements/tabs disappeared,but the subform remained on the canvas vs. the tab page it was on originally.  So, you might be able to save some effort and not need to do that, but I do appreciate the effort.  Maybe that can wait until we see the result of doing a good import

Client needs app running by end of March, still have more to do.  Have a meeting in the morning because client wants to discuss options including holding/killing the project, staying with/away from Sesame.  I am advising to stay with Sesame, but put on hold for one week to see what findings will be.  In the meantime we can work on other non-sesame tasks like exporting/parsing/formatting/validating data from old proprietary application, and converting data into ascii files that can be used in any database we finally end up using.

Thanks to the whole team for the efforts you are putting in on this.  My client will definitely be told of the team effort.

I received some files back from Ray tonight with color tables that were corrected.   

Will test them out this weekend.  Thanks lots...

Great news!   

This solution on a Friday night at 10 PM, and on a holiday weekend.   Where else is that commitment?

I told them it would not take a week. 
This is another great example of the unique support and customer service that cannot be duplicated anywhere else.   

Kudos to all.