>
>I really hate to point this out, but James's application had a bug long before it was upgraded to VFP9. The app was pretending to refresh data. New behavior made that bug clearly visible, whereas the setting would just allow it to "bloom". At the end, James's customer got an app that actually does what it is supposed to do.


Aleksey,

I wanted to respond to this remark without trying to get into any type of argument. The reason why I chose to use views in my JOIN condition was due to the JOIN limit VFP had prior to version 9.0. I had been used to working in SQL Server and was disappointed to find out VFP had this limit when I created the VFP application using VFP tables. So, to get past the JOIN limit, I used views in special cases where I needed the data. There are several other VFP developers I have spoken with in the past who have used the same solution to get past the limitation on the number of JOINS allowed in a view.

I do understand now that the difference with VFP9 that broke these eight views (Fortunatey, I only had eight views setup this way out of hundreds of views in my application) is that the JOINed views are now opened with NODATA. Where prior to VFP9, these views opened with data which is why the data was available when the main view was requeried.

For these eight views, I simply requery the JOINed views prior to requeying the main view and the problem is solved. Because only eight views were involved, it was very difficult to test (by the way, I didn't even know to look for it in the first place) this issue. It only caused a problem with certain features and my applications has many features. I did not expect to have to go through every single feature upgrading to VFP9 and I don't have a testing team to help me out, it is just me.

I just wanted to clarify why I made the decision I made and for you to say my application had a bug in it all along I believe is incorrect. I upgraded from VFP6, 7 and 8 without this problem. This only came up when upgrading to VFP9. I now understand more clearly what is going on "under the hood", created a work around and all is back to normal. Now that the JOIN limit has been lifted, I will more than likely rework these eight views. But in the meantime, the work around I put into place is working fine and I could get the problem resolved and post an update for my customers quickly.

I will say that if I responded the way you responded to me to my customers, I would be out of business. I guess because it is Microsoft, customer relation skills are not a requirement. I don't intend this in a mean way, it just was not appropriate and I hope you can see that and make adjustments in future responses to your customers.

Thanks,

James Moore MCAD, MCDBA
President
Ministry Tracking Software, Inc.