By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,391 Members | 2,182 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,391 IT Pros & Developers. It's quick & easy.

Query limited to 1000 entries

P: 2
Hi,

I am new to Access, and I am using Access 2003. I am using an ODBC data pull to get information from an application called Remedy. This application only allows a maximum of 1000 entries to be returned when queried.

I am looking to make a macro that will change the date field of an append query and continue to loop and pull more information into my table until it gets an error (No entries returned).

Does anyone have any ideas on how I could accomplish this?

Thanks in Advance!

SKiLLzCO
Aug 31 '07 #1
Share this Question
Share on Google+
3 Replies


JConsulting
Expert 100+
P: 603
Hi,

I am new to Access, and I am using Access 2003. I am using an ODBC data pull to get information from an application called Remedy. This application only allows a maximum of 1000 entries to be returned when queried.

I am looking to make a macro that will change the date field of an append query and continue to loop and pull more information into my table until it gets an error (No entries returned).

Does anyone have any ideas on how I could accomplish this?

Thanks in Advance!

SKiLLzCO
How will you know you're not pulling the same records twice?
Aug 31 '07 #2

P: 2
How will you know you're not pulling the same records twice?

Well, I'd like to add something to prevent that in the code. I'm going to need to change the query in the macro (like change the date range, or set it to >=MAX(Date), or something like that.

I'm just too noobish to know where to begin. =(

Thanks,

SKiLLzCO
Sep 2 '07 #3

JConsulting
Expert 100+
P: 603
Well, I'd like to add something to prevent that in the code. I'm going to need to change the query in the macro (like change the date range, or set it to >=MAX(Date), or something like that.

I'm just too noobish to know where to begin. =(

Thanks,

SKiLLzCO
Most of database design work occurs on paper way before you actually code anything. You must work out a process flow and a set of business rules that you then turn into some kind of logical flow. I this case, you need to ask/answer a few questions.
Since I haven't the insight about how much of this you've done, I have to rely on you to know what the limits are. But let me take a minute to help you think this through.
If remedy only returns 1000 rows, let's say you do your first 1000. Let's say we do put a time stamp on the records. In the next batch that you pull, we put in another stamp. But...how has your query changed since the first pull, to bypass the first 1000 that you pulled?
You have to ask yourself if this is the best approach? Remedy has the ability to output delimited files. These are not limited to 1000 records. You could effectively import that file using access which would render the effort you're trying now completely unneeded.
Please take a few minutes to explore Remedy's capabilities, and use those to your advantage before you try to create a very klugy type of data pull process.
J
Sep 2 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.