ok, refrase on question!!!! "SQL Limit"
- Thread starter DaniBoy
- Start date
The maximum length of the Where Condition argument is 256 characters. If you need to enter a more complex SQL WHERE clause longer than this, use the OpenForm method of the DoCmd object in Visual Basic instead. You can enter SQL WHERE clause statements of up to 32,768 characters in Visual Basic.
from VBA help.
NOTE: This states only the where clause but in my experience it means and entire statement. Try putting it into the vba instead. Hope this helps
from VBA help.
NOTE: This states only the where clause but in my experience it means and entire statement. Try putting it into the vba instead. Hope this helps
- Local time
- Today, 13:42
- Joined
- Feb 28, 2001
- Messages
- 30,554
Daniboy
Your post on a long query string with a humongous WHERE clause and this post seem to be the same problem.
A little bit of advice, here.
If you don't like the solutions given to you, don't just repost the question or beg for a solution from Pat. REPLY to the post and tell us why you don't like, don't understand, or can't use the offered solution. Tell us WHY this doesn't work for you. Don't just turn up your nose at the solutions. If we don't know WHY you can't use our proposed answers, we won't be able to give you a better answer on the next try.
We are (mostly) a bunch of altruistic folks willing to offer advice to those who are now where we were a few years ago. We can remember the frustration of dealing with a balky product. We can feel your pain. But when you just repost your question in another formulation of the same thing, all you do is frustrate us. You make us feel that we aren't helping you and that somehow explaining the problem to us is beneath you, or something equally anti-social.
So Daniboy - let's have a little bit more give-and-take here.
What gives with your long query problem?
Your post on a long query string with a humongous WHERE clause and this post seem to be the same problem.
A little bit of advice, here.
If you don't like the solutions given to you, don't just repost the question or beg for a solution from Pat. REPLY to the post and tell us why you don't like, don't understand, or can't use the offered solution. Tell us WHY this doesn't work for you. Don't just turn up your nose at the solutions. If we don't know WHY you can't use our proposed answers, we won't be able to give you a better answer on the next try.
We are (mostly) a bunch of altruistic folks willing to offer advice to those who are now where we were a few years ago. We can remember the frustration of dealing with a balky product. We can feel your pain. But when you just repost your question in another formulation of the same thing, all you do is frustrate us. You make us feel that we aren't helping you and that somehow explaining the problem to us is beneath you, or something equally anti-social.
So Daniboy - let's have a little bit more give-and-take here.
What gives with your long query problem?
DaniBoy
Registered User.
- Local time
- Today, 19:42
- Joined
- Nov 18, 2001
- Messages
- 174
I'm sorry guys!!!!
I know I was a little inpatient with this question, fisrt I thought I was not explaining my self well enough, then from seeing people reading and not replying I realy thought I was not explaining my problem right, so I asked with out putting all the code. After viewing that I had no results, I got even more confuse on how to input my question. It wont happen again, and I will try to contain my frustration!!!!
.... Well, the problem was that I have to many text characters, I will try the vb explanation.
Thanks
DaniBoy
I know I was a little inpatient with this question, fisrt I thought I was not explaining my self well enough, then from seeing people reading and not replying I realy thought I was not explaining my problem right, so I asked with out putting all the code. After viewing that I had no results, I got even more confuse on how to input my question. It wont happen again, and I will try to contain my frustration!!!!
.... Well, the problem was that I have to many text characters, I will try the vb explanation.Thanks
DaniBoy
BLeslie88
B Leslie
- Local time
- Today, 19:42
- Joined
- May 9, 2002
- Messages
- 228
VBA will work...
The reply on VBA coding was accurate, I do most of my sql in VBA now and have never had limitation problems. It even allows you more control over user driven queries that need variables for filters....
Note that in VBA you need to use small quotes ' instead of double quotes "
Also you may have trouble trouble shooting sql in VBA at which time I suggest copying it back into a query and testing it, unless again your character limit has been busted.
Also consider shorter naming conventions that are more concise.
Good luck...
The reply on VBA coding was accurate, I do most of my sql in VBA now and have never had limitation problems. It even allows you more control over user driven queries that need variables for filters....
Note that in VBA you need to use small quotes ' instead of double quotes "
Also you may have trouble trouble shooting sql in VBA at which time I suggest copying it back into a query and testing it, unless again your character limit has been busted.
Also consider shorter naming conventions that are more concise.
Good luck...
Similar threads
