OK I solved the first problem by converting the fields from text to memo. (That's not really a solution but it took care of the immediate issue.) The second problem turned out to be invalid ASCII characters in the memo fields. Apparently the data entry folks are sometimes clumsy on the keys. But now I have a third new problem. While importing a very large XML (39 meg) consisting of an integer field and a memo field, Access gets to around 1300 records and then hangs with no error messages at all. My various data checkers don't find any problems with the data. More ideas?


>Check for values in the numeric fields that are bigger than filed definition specifies. For example
>

>CREATE CURSOR test (num N(3,1))
>INSERT INTO Test VALUES(999)
>BROWSE
>

>As you can see 3 digits number is stored in a field that suppose to allow only 1 digit before decimal point.
>
>>I am using XML to transfer a VFP database to Access using the commands
>>

>>CURSORTOXML(lcTable, "c:\myXMLFile.xml", 1, 512, 0, "mySchema.xsd")
>>oAccess.ImportXML("c:\myxmlfile.xml")
>>

>>
>>This seems to work almost perfect except that one of the tables produces Access import errors that say "Microsoft JET Database Engine: The field is too small to accept the amount of data you attempted to add." or "Microsoft JET Database Engine: Update or CancelUpdate without AddNew or Edit.". The errors occur on only a few of the records.
>>The table structure of the Access table appears to match that of the VFP table as far as field widths go. Can someone give me a clue as to what's happening here?