P
Peter
I am attempting to import an XSD schema file into MS Access 2007. It is the
goal to have a database structure (tables and relationships) automatically
created.
Doing so with the complete XSD file MS Access crashes every time (with the
only choice of sending or not sending the error report).
Then I tried to minimize the XSD file to an absolute minimum. The success
was encouraging as the import worked and some tables and relationships have
been created.
Now I needed to know what components of the original XSD file causes the
crash. Therefore I re-inserted the removed parts step by step and repeated
the import after each insertion.
And that's where things started to become weared: at some point the
import failed again. But after removal of what I just inserted, Access crashed
again. Furthermore it happend that with the same XSD file it sometimes worked
and somtimes didn't. It behaves just inconsistently.
I got the impression that the success was more dependant on the exact order
of my import procedure rather than from the XSD content.
(The problem occurs regardles of whether I just import the XSD or I import
an XML which refers to the XSD)
Did anybody experience similar problems?
Are there any relevant system paramters?
Are there any unsupported XML/XSD constructs?
thanks in advance for all your help.
kind regards,
Peter Sempert
goal to have a database structure (tables and relationships) automatically
created.
Doing so with the complete XSD file MS Access crashes every time (with the
only choice of sending or not sending the error report).
Then I tried to minimize the XSD file to an absolute minimum. The success
was encouraging as the import worked and some tables and relationships have
been created.
Now I needed to know what components of the original XSD file causes the
crash. Therefore I re-inserted the removed parts step by step and repeated
the import after each insertion.
And that's where things started to become weared: at some point the
import failed again. But after removal of what I just inserted, Access crashed
again. Furthermore it happend that with the same XSD file it sometimes worked
and somtimes didn't. It behaves just inconsistently.
I got the impression that the success was more dependant on the exact order
of my import procedure rather than from the XSD content.
(The problem occurs regardles of whether I just import the XSD or I import
an XML which refers to the XSD)
Did anybody experience similar problems?
Are there any relevant system paramters?
Are there any unsupported XML/XSD constructs?
thanks in advance for all your help.
kind regards,
Peter Sempert