Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3706
  • Last Modified:

ODBC error on very large linked table in Access

I think I know the answer to this but need confirmation.  Access is used as a front end for a large database on a server.  All the tables are linked and reports are run against the data.  One table opens with #Name? in all fields and ODBC error message.  However, the ODBC connection is the same as the other tables which show up with no problem.  I believe it is because the table is so large that Access can't open it.  We have made several smaller Access databases that link only to this one table and created local tables with only one year's worth of data in each one.  The total of all the years data is several gigs.  Is this why we can get the data through queries and reports but not see the data in the table?  We can see the field headings in the table, however.

Thanks,
LindaOKState
0
LindaOKSTATE
Asked:
LindaOKSTATE
  • 6
  • 4
  • 2
  • +2
4 Solutions
 
danishaniCommented:
It might indeed caused by the large amount of data, causing an ODBC TimeOut error probably.
Check your TimeOut settings, just in case.
But I am not entirely sure about that if that's the main reason.

Another source to look into is a permission issue. Sometimes can lead into this kind of behavior.

You may try to delete the link, and re-create it and see if that helps.

Do you had any error message returned?
That might also help to search for more specific direction.

Hope this helps,
Daniel
0
 
AnuroopsunddCommented:
by default ODBC timout in Access is 60 seconds... change the value to 0 and try...

http://www.techonthenet.com/access/queries/timing_out.php
0
 
LindaOKSTATEAuthor Commented:
I have relinked the table several times.  Same thing, ODBC error.  On the time out issue, where would you change ODBC timeout for a table?  It is not a query that gives the ODBC error, it is just opening the table.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AnuroopsunddCommented:
ODBC connection makes the connection to the database and query the table ...
change the value and try if it makes the difference.. screenshot in above link.
0
 
LindaOKSTATEAuthor Commented:
I do not understand.  The screenshot is for a query.  How do you change it for just a link to a table?
0
 
Kelvin SparksCommented:
I do not believe it is ODBC. While ODBC is sloww (about 1000 records per second), it will start to display data on your screen while still retrieving data.

Yes you are right, there's no timeout for a table linked via ODBC - yes to a query . The #name issue is generally a data reading issue. I guess it is possible that if the data were to cause the access database to exceed its maximum size (somewhere between 2 and  4 GB depending on versions) then it may spit the dummy. Can you create a view on the server that limits that data to around 100,000 records and see what happens. The table doesn't happen tho have more than 256 colummns, or more than 32 indexes??


Kelvin
0
 
DSTECH_ADMIN_01Commented:
Hi Linda,

What kind of backend are you using? Sql server or Oracle?
Are you connecting through an ODBC driver? That is the place where you can set your timings.

But when opening your table it does a full tablescan, and as you might know ODBC has its limitations. What was the situation before? There was a period your application worked well. Did the table schema changed? DataType change, column naming change?

You might concidering PASS-THROUGH queries to query your full table.
0
 
LindaOKSTATEAuthor Commented:
Intersystems Cache sql server.  The table is probably over 4 gigs.  I do not know the situation previously.  I am a consultant trying to clean up some things after the person in charge of this database left.  The particular table has 73 columns.  I really do not need to see the whole table, it has about 12 years worth of data in it.  I am just trying to figure out what is going on with the table so I can explain to the client.  Since all the other tables open with the same ODBC connection AND we can query and report on the table that won't open, my theory is that a 4+ gig table just can't be opened in Access, therefore, the ODBC error.  The error says:
ODBC--call failed.  It shows 76 records with every field showing #Name?, although it shows the proper field titles.  It will also let you look at the table design, showing all the field titles and the primary keys etc.  It is a concatenated key of 4 fields.
0
 
DSTECH_ADMIN_01Commented:
Hi Linda,

Create a new database.
Relink the 4GB table using the configured DSN.

Create another database or use the same database
Create a Pass-through query using the configured DSN.

What happens?

The Access database jet engine has its limitations. But you are not using the database engine when using ODBC. Everything goes through the ODBC connection. So showing a fulle sized table should work just fine. But correct me if I am wrong.

Danny
0
 
LindaOKSTATEAuthor Commented:
I did a pass-through query, got the same error with the #NAME? in all fields.  i added up the records from all the yearly data in local tables.  there are almost 6,000,000 records
0
 
DSTECH_ADMIN_01Commented:
Hi Linda,

It worked? What did you find out?

Danny
0
 
LindaOKSTATEAuthor Commented:
I could do a pass though query on a limited number of fields but the whole table (select *) gave the same error message about ODBC failed and #NAME?.  I decided the error is with the size of the table and let it go at that.
0
 
DSTECH_ADMIN_01Commented:
Hi Linda,

A pass-through on a limited number of records. How many until the error occured?
It could be an ODBC memory issue. Depending on the driver software.

Danny
0
 
LindaOKSTATEAuthor Commented:
56 with the query, 72 or so when i tried just to open  the table without a query.

Linda
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 6
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now