Hi!
Possible cause also:
When you have pending changes in the view, requery() does try to update daa automatically. When SQL Where clause is too long, you will receive this message too. Change options in view designer to include only key fields in the SQL Where clause.
Havo no other ideas, maybe someone else jump in...
HTH.
>Hi Vlad,
>
>Just what I was looking for... The total character count for the expanded SQL was 1,715 so I'm not sure why it is failing.
>
>Renoir
>
>>CursorGetProp("SQL")
>>
>>However, if you have a parameter like "&?lcWhere" and lcWhere contains too long string - here is a problem. SQL Statement in VFP could not be longer than the command line limit (~8000 characters) after expanding of all macros.
>>
>>There are several ways to make SQL Statement shorter...
>>
>>>I'm getting an "SQL statement too long" error during Requery of a view. While in debug mode can I view the actual SQL being used to generate the view? I know I can see the original code in the view designer, but what about during execution? Thanks!
>>>
>>>Regards, Renoir
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.