AspWebSolution Forums » Products » ASP Report Wizard v2 » Your filter is invalid! Message

index | search | no replies | posting guidelines | help

login | register

» »

:: Your filter is invalid! Message :: (11)

Post a New Message | Post a Reply

Sep 3 2005, 11:28 AM

Your filter is invalid! Message

MindTelligent

since: May 10, 2005
from: El Dorado Hills, CA Report Version2.0.577
---------------------------------
I have 2 database schemas for two different profitcenters, running on the same application server. The databases objects are exactly same. I am using same reports code but in two different IIS Virtual Directory.

The default.asp files are exactly the same but only differ in the connectivity to different databases.

One set of report works fine but the other gives me this error.

Your filter is invalid!
[JobTable].[StartDate] = '9/15/205'

These are very critical reports. Please help

Sep 6 2005, 6:09 AM

Re: Your filter is invalid! Message

ghost

from: Washington, DC [JobTable].[StartDate] = '9/15/205'

I don't think the year 205 will compute as a valid date in SQL Server or Access.

-------------------------
Ghost

Sep 6 2005, 9:17 AM

Re: Your filter is invalid! Message

MindTelligent

since: May 10, 2005
from: El Dorado Hills, CA Actually the date I entered was 09/15/2005

Please help

Sep 6 2005, 1:56 PM

Re: Your filter is invalid! Message

ghost

from: Washington, DC This seems to be a bug with Access. We are hoping to fix it before the next release.

thanx!

-------------------------
Ghost

Sep 7 2005, 7:54 AM

Re: Your filter is invalid! Message

MindTelligent

since: May 10, 2005
from: El Dorado Hills, CA I observed this issue while using SQL Server

Thanks for all your help!!!

Sep 8 2005, 12:53 PM

Re: Your filter is invalid! Message

Stever

since: Sep 1, 2005
from: somewhere This particular bug breaks a function I use often, is there any type of timeline anticipated for a fix (days, weeks)?

Also, if I purchase the program could I get an earlier version that doesn't have the date expired 'security feature'?

Thank you

Sep 8 2005, 1:15 PM

Re: Your filter is invalid! Message

ghost

from: Washington, DC Can you please explain how it breaks a function you used to use!
So we can trace it better.

P/S: The date check and other security checks only happens when no license key has been set. This check is just to make sure that free versions are not reused within third party commercial applications

-------------------------
Ghost

Sep 8 2005, 1:26 PM

Re: Your filter is invalid! Message

Stever

since: Sep 1, 2005
from: somewhere If I create a report that uses a filter involving a date, or create a report and then try to apply a filter involving a date, I get an error.

Filter example - applying the filter "time > '7/28/05' " to an existing report generates the error

Your filter is invalid!
[HELPME].[TIME] > '7/28/05'

If I attempt to use this formula as a condition when creating an ASP report it gives the error "Invalid Search Condition". I can still create or filter with name, type or other fields, it just gacks at using a date.

This worked before upgrading to the newest version last Friday, neither the database or the actual report formats were altered.

Sep 8 2005, 2:14 PM

Re: Your filter is invalid! Message

ghost

from: Washington, DC It seems the report wizard cannot recognize database type from your connection string.
try this:
add the following statement before you initialize your connection string depending on you database type:

objWiz.DatabaseType = "ACCESS" ' or "MySQL" or "SQLSERVER"

If your database is MS Access, then the bug fix (when filtering) will be available before the end of tomorrow.

-------------------------
Ghost

Sep 9 2005, 2:43 PM

Re: Your filter is invalid! Message

Stever

since: Sep 1, 2005
from: somewhere Thanks! I didn't get a chance to implement the fix before you posted the new version, I will try this and post back if I have any questions.

Sep 9 2005, 5:52 PM

Re: Your filter is invalid! Message

MindTelligent

since: May 10, 2005
from: El Dorado Hills, CA I have tried putting the database type as you mentioned. It does solve the issue.

I am using SQLSERVER and have purchased the version of the software. I have added the security key in the default.asp

Please help

Pages: (1) [1]