Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with XMLtoCursor

Status
Not open for further replies.

baseballgem

Programmer
Oct 3, 2001
54
US
I'm still having a problem converting an XLM file to a cursor.
I have VFP 8 which (I thought) was suppose to have the correct dlls. an msm*3 and msm4 - I loaded in all the SOAP stuff that was reccommended.
But I still get this.
System cannot locate the file msxml3.dll
XMLTOCURSOR("c:\client23\testjunk.xml",'docstemp2',512)
-------------------
In another try I get

XML Parse error. Ivalid at the top level of the document Line 1 Position 1.
c:\client23\testjunk.xml
XMLTOCURSOR("c:\client23\testjunk.xml",'docs1',8192)

---------------------------------
Also, in the help - what does this mean when it says...
"..However, this does not work for XML provided from an external source or with XML that is not generated with the CURSORTOXML( ) function."

Does this mean if I receive some XML file generated out of .Net or elsewhere that I can not convert it to a cursor in VFP8?
 
Also, in the help - what does this mean when it says...
"..However, this does not work for XML provided from an external source or with XML that is not generated with the CURSORTOXML( ) function."

Does this mean if I receive some XML file generated out of .Net or elsewhere that I can not convert it to a cursor in VFP8?


I would say, yes, that is what it means. VFP can deal with its own format of XML, but has problems when XML data comes from another source. I would suggest you create a parser program that could handle the XML data you are receiving (In other words create your own XMLtocursor function).


System cannot locate the file msxml3.dll

This code indicate that this DLL is either missing or not properly registered. But I don't think is it part of SOAP. XML parser is a separate download and install [ignore][][/ignore]


Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
Does that mean that even though the 2 files
msxml4.dll and msxml3.dll are certainly there in C:\WINNT\SYSTEM32

...that, in addition, one must "register" each of them in the registry: Even though I have a full professional version of VFP 8 installed. I know how to do that; just seems odd.
 
Even though I have a full professional version of VFP 8 installed.

Yes they do have to be registered. And VFP professional is unrelated to the Microsoft XML parser, they are two different products.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
baseballgem,
The XML file parse error is caused by wrong nflag to xmltocursor(). Instead of 8192 it shall be 8192+512=8704. 512 means:
"Specifies that the first parameter, either an eExpression or a cXMLFile, is a string containing the name and path of an XML data file."

/Micael
 
:) Aware of that but happened to see this thread when searching for xml stuff. Who knows, some day someone might find the info useful.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top