>The views are JOINed, not included in the FROM clause.

You don't realize that LEFT OUTER clauses in your query are actually parts of the FROM clause?

> Let me clarify my last post. I understand the views are all opened NODATA. The change is in the REQUERY(). In VFP8, REQUERY() would requery the views in the JOIN's as well as the main view. This worked perfectly. Now, in VFP9, REQUERY() does not requery the JOIN'ed views so zero records are returned. This to me is a BUG! Why would this change from VFP8 to VFP9? Your comment about "blindly" is just not right. You mean REQUERY() was magic before and now it is not. Sounds like someone is just trying to CYA or why else would you try to direct this problem back on my plate. REQUERY() worked in this scenrio prior to VFP9, plain and simple. Now, IMHO, REQUERY() is broke. I really have nothing else to say about this issue other than it is broke, I found a workaround and soon my backend will be SQL Server and all this will be behind me. It was just a bad experience to go through and really upset a lot of my customers.
>

James, you DIDN'T UNDERSTAND A THING.
REQURY doesn't REQUERY views in FROM, never did (including VFP8). If it finds cursors for those views it'll use data from them, no REQUERY is done for those cursors. Your app didn't open those cursors explicitly, they were left opened by USE ... NODATA command. Whether those cursors are going to be empty or not empty is not documented. If behavior is not documented, it is subject to change from version to version. Therefore, it would be wise not to rely on not documented behavior, especially when you don't understand why you are getting particular result.