The original has only 1 number field (integer) and it is being translated to long integer in the Access table. There is also a datetime field and 5 text fields. The text fields are translated with the same length as the originals (60 characters) and the datatime field seems to import ok..


>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?