ok, the joke is gone but for clarity the original poster mistakenly said "n o s e" not "n o i s e". I was making a joke - lighten up.

>Right....the VFP team could make some noise. My question is why should they make noise.
>
>The why is far more important than the could....
>
>My reading is fine...
>
>
>
>
>>OK, besides jumping to conclusions you also dont read well :) Read my post again...
>>
>>>Why should the VFP team make "noise" about it...???
>>>
>>>>PMFJI John, but he didnt say some noise had to be made. Just that the VFP group could make some "nose" about it. Really, you do jump to conclusions ;)
>>>>
>>>>
>>>>>Why should noise be made? Why do you feel there is an ENTITLEMENT that VFP be used? How is your life affected one way or another because the .NET team decided to use jet as opposed to VFP? More importantly, do you think ANYBODY on the VFP team cares about the fact that the .NET team used Access instead of VFP?
>>>>>
>>>>>FWIW, Access is not the piece of junk a lot of VFP developers like to make it out to be. For one thing, it has better integration with SQL Server than VFP ever has or will ever have.....
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I was just looking through the latest issue of Visual Studio Magazine, and there is an article on Whidbey ASP.NET features. One of the new features is automated membership/security management in VS.NET; a tool automatically appears to create a database called ASPNetDB.mdb is made to hold credential and personalization info, with the expectation that the database would be upsized to MsSql when needs grow.
>>>>>>
>>>>>>The fact that a Jet database was used instead of a VFP one makes me a little sick. I find it hard to believe that in 2004, the "new technology" Whidbey team would use an MDB when the DBC has so many advantages as an ISAM store.
>>>>>>
>>>>>>I hope someone at the VFP group can make some nose about this.