Aidan, I have had this happen before. Possibly the first few records being imported have numbers in this field and Access is assigning this field a number data type. Then when it encounters the "A" in the middle of your problem field, it gives the "Type Conversion Failure"...
Maybe getting that appropriate field is the answer for me. If I could use the built-in dBase driver, it would save me a lot of heartache. Is there any way I can know what type of field needs to be in the table for me to link to it that way?
Dear rgbean, when I look at the design of the linked table in Access, I find that most of the fields are marked with a key. I have tried to look at the structure of the tables in FoxPro 2.6, but I am not able to see which fields are marked as a primary key. I have also tried linking the files...
I am attempting to append to FoxPro 2.6 files from Access XP. I am using the most current VFP driver and can link and import with no problem. However, when I export or append back to the 2.6 files, number fields, dates, and even some character fields don't append. I am getting a key violation...
Can someone give me some advice on how to connect to FoxPro 2.6 using Access XP or setting up a connection string in a Visual Basic application? Thanks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.