Hi all



I have some data in Visual Foxpro which I am converting via the ODBC 

import in access to work in a web app via ASP.



VFP reports the length of the fields in one table as 2.4kb 



The import crashes out with a "record too long" error. I'd be surprised if 

access can't handle a small ish table like this so is it likely to be a 

problem with the data itself.



A couple of the fields are big 254, character note fields but the rest 

about 180 fields are fairly straight forward.



I am just about to start writing code to drop out the "insert into table" 

commands to see if that works or try a non odbc import ie dBase or CSV.



I'd really appreciate any comments as to whether I am onto a loser here.

Its quite late in the day to start splitting the file down, the file in 

question doesn't really lend itself to this in any case (masterfile for 

vehicles and plant equipment)

Does SQL Server have the same problem? The database will be upsized fairly 

soon.



Thanks in advance



Regards

Graham

You may wish to try using VFP's export routine to send it to a CSV file that

you can then parse via VB.



Walt

> You may wish to try using VFP's export routine to send it to a CSV file 

that

> you can then parse via VB.

> 

> Walt

> 



Hi 



Thanks for the reply.



So access does support records longer than 2k then?



The "record too long " error suggests splitting the data up into different 

tables which I thought was strange.



Regards

Graham