Make - table
- Thread starter prabhu
- Start date
boblarson
Smeghead
- Local time
- Today, 09:50
- Joined
- Jan 12, 2001
- Messages
- 32,040
What is the source for this make table? Just like Namliam said, it sounds like you are getting way too many records for Access to handle.
MSAccessRookie
AWF VIP
- Local time
- Today, 12:50
- Joined
- May 2, 2008
- Messages
- 3,423
Like the others have said, it sounds like the "Invalid Argument Error" that you are getting is either creating extremely large records, or an extremely large number of records. Can you show the code for the Make Table so that perhaps we can help you to determine which it is and why.
Not only the # of records but also the size of the records.
Try importing say 1000 records and see how big your database gets. Access has a size limit of 2 gig.
Why copy 1 mio records from a ODBC source? why not query the source directly?
Try importing say 1000 records and see how big your database gets. Access has a size limit of 2 gig.
Why copy 1 mio records from a ODBC source? why not query the source directly?
Thank you Namliam,
Acutally i am new to access,one of my collegue told me that when we run the queries (big queries) directly from ODBC tables it will take time for the query to give result and he suggested to create the copy of the tables in my local drive or share drive using make table and link those make tables to get the results fsater from query. I am runing this make tables daily to replicate the database in my drive using make table. am i in a right direction?
Acutally i am new to access,one of my collegue told me that when we run the queries (big queries) directly from ODBC tables it will take time for the query to give result and he suggested to create the copy of the tables in my local drive or share drive using make table and link those make tables to get the results fsater from query. I am runing this make tables daily to replicate the database in my drive using make table. am i in a right direction?
Usually a database you would connect to with ODBC would be based on a server which (usually) is a lot more powerfull than your local machine? I dont understand this ??
Unless you are connecting into multiple ODBC sources you shouldnt be duplicating the data, instead you should run the (proper) queries on the source system. That is unless there is a VERY good reason to duplicate, like you want to run some heavy duty queries on a production system that is allready strapped for resources
Unless you are connecting into multiple ODBC sources you shouldnt be duplicating the data, instead you should run the (proper) queries on the source system. That is unless there is a VERY good reason to duplicate, like you want to run some heavy duty queries on a production system that is allready strapped for resources
dfenton
AWF VIP
- Local time
- Today, 12:50
- Joined
- May 22, 2007
- Messages
- 469
You colleague is giving advice that falls apart if you give it any thought at all.
If you query the ODBC database directly, it returns the results, say 1,000,000 records.
If you copy the data for querying, you have to pull down the 1,000,000 records and only then query them for what you want to know.
You're pulling down the 1,000,000 records either way, so it seems obvious to me that you'd be better of querying the ODBC data source directly and not copying the stuff down from the server.
There are some exceptions to that basic principle involving temp tables for complex queries that take a lot of time to process, but this sounds like it's just a lot of data, not necessarily a complicated query.
If you query the ODBC database directly, it returns the results, say 1,000,000 records.
If you copy the data for querying, you have to pull down the 1,000,000 records and only then query them for what you want to know.
You're pulling down the 1,000,000 records either way, so it seems obvious to me that you'd be better of querying the ODBC data source directly and not copying the stuff down from the server.
There are some exceptions to that basic principle involving temp tables for complex queries that take a lot of time to process, but this sounds like it's just a lot of data, not necessarily a complicated query.
Similar threads
