|
Home > Archive > MS Access project with SQL Server > October 2005 > Filters more than 255 characters
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Filters more than 255 characters
|
|
| Ryan Langton 2005-10-27, 8:32 am |
| I have filters I have to apply to an access form that are more than 255
characters:
Division IN ('Administration','R
ecreation',.... etc. to beyone 255
characters.
When I watch the ServerFilter or Filter properties in my watch list they are
always cut off at 255 characters. Is there any way to use the longer
filters? Also should I be using the Filter or ServerFilter property?
Thanks.
Ryan
| |
| Ryan Langton 2005-10-27, 8:32 am |
| Hmmm it does appear the Filters are holding over 255 characters now, it must
have been one of my string variables cutting them off. However, the filters
still seem not to be working. On the form I have Allow Filters = True, but
setting Me.Filter and then doing a Me.Requery does not seem to apply the
filter. Do I have to use the ServerFilter property instead?
"Ryan Langton" <langton@ci.manhattan.ks.us> wrote in message
news:eqLIXfL1FHA.1032@TK2MSFTNGP12.phx.gbl...
>I have filters I have to apply to an access form that are more than 255
>characters:
> Division IN ('Administration','R
ecreation',.... etc. to beyone 255
> characters.
> When I watch the ServerFilter or Filter properties in my watch list they
> are always cut off at 255 characters. Is there any way to use the longer
> filters? Also should I be using the Filter or ServerFilter property?
> Thanks.
>
> Ryan
>
| |
| Robert Morley 2005-10-27, 8:32 am |
| If you're doing it programmatically, you've probably missed the "Me.FilterOn
= True" part. Just add that right after Me.Filter, and it should be fine.
I believe whenever you execute that, it automatically requeries, but I don't
have Access handy on this computer, so you'll have to test it yourself and
make sure.
Rob
"Ryan Langton" <langton@ci.manhattan.ks.us> wrote in message
news:eGJjKoL1FHA.4004@TK2MSFTNGP10.phx.gbl...
> Hmmm it does appear the Filters are holding over 255 characters now, it
> must have been one of my string variables cutting them off. However, the
> filters still seem not to be working. On the form I have Allow Filters =
> True, but setting Me.Filter and then doing a Me.Requery does not seem to
> apply the filter. Do I have to use the ServerFilter property instead?
>
> "Ryan Langton" <langton@ci.manhattan.ks.us> wrote in message
> news:eqLIXfL1FHA.1032@TK2MSFTNGP12.phx.gbl...
>
>
| |
| aaron.kempf@gmail.com 2005-10-27, 8:32 am |
| so in which ORDER should you do this?
what is the best way to apply a filter to make sure that it doesnt do
more requerying than it needs.
I mean.. for starters
IF Me.Filter <> "ROWID = 312" Then Me.Filter = "ROWID = 312"
IF Me.FilterOn <> True then Me.filterOn = True
that would be more efficient. RIGHT?
-aaron
| |
| Ryan Langton 2005-10-27, 5:30 pm |
| Robert,
You're right, I just forgot to set the Me.FilterOn = True.
I went through my code and added that after every Me.Filter = myVar
statement and everything works great now.
Thanks,
Ryan
"Robert Morley" <rmorley@magma.ca.no.freakin.spam> wrote in message
news:uTsY$JN1FHA.1168@TK2MSFTNGP10.phx.gbl...
> If you're doing it programmatically, you've probably missed the
> "Me.FilterOn = True" part. Just add that right after Me.Filter, and it
> should be fine. I believe whenever you execute that, it automatically
> requeries, but I don't have Access handy on this computer, so you'll have
> to test it yourself and make sure.
>
>
>
> Rob
>
>
> "Ryan Langton" <langton@ci.manhattan.ks.us> wrote in message
> news:eGJjKoL1FHA.4004@TK2MSFTNGP10.phx.gbl...
>
>
|
|
|
|
|