>We implemented recognition of our own schemas, ADO Recordset schemas, and some SQL XML. Due to the time constraints imposed by our freeze for RTM, we implemented XSD schema that conformed to the W3C working draft at the time, as implemented by Microsoft. The W3C made a final recommendation subsequent to our freeze date. There should be a note in either the Doc's or the Readme that note that the final implementation of XSD schema will not be until a later Service Pack or Release of Visual FoxPro. Thus, in our RTM release, we are not fully compatible with VS .Net or SQL XML, as we knew that both of these products would be changing and/or implementing XSD schema after our RTM date. Thus, it is our goal to be as fully interoperable as possible with VS .Net and SQL Server XML in the VS .Net RTM timeframe.
Today I tried XmlToCursor on a .vdx file exported from Visio 2002, and it does have a hierarchical structure. It produced a decent cursor, though, but for the lower levels in the hierarchy it just unpacked the values without descriptors into a memo field. Just an idea - it would be nice if these lower levels would remain as XML per se in these memos, so we could drill down programmatically if needed. Or if any other means of drilling down the hierarchy was available - maybe by supplying some names from the previous level.
I found a piece which interested me, pasted it into a separate text:
- <Shape ID="11" NameU="Tab control" Type="Group" Master="3">
- < XForm>
< PinX>4.1387795275591< /PinX>
< PinY>8.2572588582677< /PinY>
< Width>6.4468503937008< /Width>
< Height>4.351624015748< /Height>
< LocPinX F="Inh">3.2234251968504< /LocPinX>
< LocPinY F="Inh">2.175812007874< /LocPinY>
< Angle Unit="DEG" F="Inh">0< /Angle>
< FlipX F="Inh">0< /FlipX>
< FlipY F="Inh">0< /FlipY>
< ResizeMode F="Inh">0< /ResizeMode>
< /XForm>
(had to insert a space after each < so UT wouldn't think it's a HTML tag) and that part imported fine, except that the last four zeros came in as .f., i.e. logical fields.
Other than this, the thing works just great and blazingly fast. Explorer choked on this file - it was about one megabyte long.
>Note I will be at San Diego DevCon, and would be happy to hear your suggestions and issues. I will be back in the office on 9/13.
Wish I made it at to at least one conference these years ;)
