Hi Sergey,
I've verified that there is data for the dates involved. I've also verified that the view works if there is no data for the dates involved.

The view is very long, 117 fields including , 6 udfs() that do there own Select(), 4 tables involved (only 1 updatable).

I have discovered something else. And I'm pretty sure that it's not the data involved.

It only happens on REQUERY(). If I "USE [ViewName]", it works fine, but if I then REQUERY() it crashes. Naturally it crashes in my form, because I always start with NODATA then REQUERY() when I need it. If I can't figure out what is happening, I'll change my REQUERY() to USE in my grid (can't say I like that idea).

I've been studying Rushmore lately, and think I may be onto where the problem might be.
I actually have 3 date parameters:
between( Date1, ?pd1, ?pd2 ) and ;
between( Date2, ?pd3, ?pd4 ) and ;
between( Date3, ?pd5, ?pd6 )
I just set the ones I want. example:
pd1 = {4/6/2}
pd2 = {4/6/2}
pd3 = {}
pd4 = {12/31/9999}
pd5 = {}
pd6 = {12/31/9999}
I'm thinking that the filters that aren't being set are returning too much data for my computer to handle prior to applying the parameters that is set.





>Do you have any data for the dates that generate error? Can you post View's SQL?
>
>>I'm simplifying this untill someone asks for details.
>>
>>I have a parametized view that I've been using for 1 1/2 years with no problem. All of a sudden I'm getting "view definition has changed" SOMETIMES when I try to open it.
>>
>>One of the parameters is "cs_Date>=?pdBegin and cs_Date<=?pdEnd".
>>I've discoverd these results:
>>

>>pdBegin    pdEnd     Results
>>Single Date Range
>>{4/3/2}    {4/3/2}   Opens
>>{4/4/2}    {4/4/2}    Error
>>{4/5/2}    {4/5/2}    Error
>>{4/6/2}    {4/6/2}    Error
>>{4/7/2}    {4/7/2}   Opens
>>Multi Date Range
>>{4/4/2}    {4/10/2}  Opens
>>{4/4/2}    {4/5/2}   Opens
>>{4/5/2}    {4/6/2}   Opens
>>

>>
>>I've tried reindexing the table.
>>I orginally guessed that I had corrupted data, but couldn't see it. But no other form or report or browse has a problem with the data. I haven't started trying to track down a particular record that might be causing this, but after those last two results, I'm wondering if it's even worth trying.
>>
>>TIA