Error when trying to use a text file with two columns as a data source
Hi!
I'm getting errors when I try to use a text file of 2.99 GB as data source. I get an error message telling me the file contains no data, even though I can open the file in other applications.
Looking forward to any hints on what may be causing this.
I'm getting errors when I try to use a text file of 2.99 GB as data source. I get an error message telling me the file contains no data, even though I can open the file in other applications.
Looking forward to any hints on what may be causing this.
Some discussion here may assist:
https://www.experts-exchange.com/questions/21306710/Access-database-size-limit.html
Are you trying to import the data, or as your question suggests, using this as a data source?
As Cactus data suggests, splitting this into smaller chunks may reveal your problem.
Cheers
JC
https://www.experts-exchange.com/questions/21306710/Access-database-size-limit.html
Are you trying to import the data, or as your question suggests, using this as a data source?
As Cactus data suggests, splitting this into smaller chunks may reveal your problem.
Cheers
JC
Yes, please clearly describe specifically what you me when you say: " I try to use a text file..."
"*Use* a file"?
Use a file how? in what application, ...etc
"*Use* a file"?
Use a file how? in what application, ...etc
ASKER
Hi boag2000. The information you request regarding details of which application I use is listed beneath the question, as well as above. Data source can mean numerous things. In this case it is simply a plain text file with two columns containing data.
ASKER
Hi, sorry for the delay.
It is a 2.99 GB text file containing data. When I'm trying to use the "Connect to datasource" I get the error. I'm not trying to import the data into access since there is a maximum limitation on the number of records in Access.
I will try it in the 64 bit version of Access instead to see if that works.
It is a 2.99 GB text file containing data. When I'm trying to use the "Connect to datasource" I get the error. I'm not trying to import the data into access since there is a maximum limitation on the number of records in Access.
I will try it in the 64 bit version of Access instead to see if that works.
I believe my original comment is still valid.
Copy a small portion of the file - some hundred KB - and import/attach that.
If it works, your issue is a too large file for Access.
If it doesn't, you will have to adjust the file somehow, no matter the size/length of it, until success. At that point, try with the full file (modified). If that fails, you are back to my original comment.
/gustav
Copy a small portion of the file - some hundred KB - and import/attach that.
If it works, your issue is a too large file for Access.
If it doesn't, you will have to adjust the file somehow, no matter the size/length of it, until success. At that point, try with the full file (modified). If that fails, you are back to my original comment.
/gustav
I tend to agree with CD, file size is most likely the issue.
Is your data file csv or txt, or some other format?
Can you also elaborate on "Two columns of data"
Cheers
JC
Is your data file csv or txt, or some other format?
Can you also elaborate on "Two columns of data"
Cheers
JC
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> The number of records is to large for MS Access.
> The number of maximum records is approx. 255 000 ..
No. Access can easily handle that count of records. Problem is the total file size which - as you have seen - Access can't grasp.
You still haven't told if the simplest solution - to split the file into smaller chunks - works for you.
Of course, importing/attaching the file to, say, SQL Server may present a work-around but that was not your original question.
/gustav
> The number of maximum records is approx. 255 000 ..
No. Access can easily handle that count of records. Problem is the total file size which - as you have seen - Access can't grasp.
You still haven't told if the simplest solution - to split the file into smaller chunks - works for you.
Of course, importing/attaching the file to, say, SQL Server may present a work-around but that was not your original question.
/gustav
ASKER
Experience.
/gustav