>>Ed,
>>
>>I beleive the point was why the lack of security... I'm sure this is a feature that we would all agree would give VFP more credibility.
>>Yes, we have the option to use Oracle, SQL Server et al. Yes, I'm sure that for VFP to equal those products would make it more costly.
>>But surely it could not be that hard to build in some user level access without having to completely duplicate their functionality..?? We all love the rich functionality of VFP but MS almost seems embarassed to admit it is part of their official development platform.
>>Don't get me wrong, I'm just tired of having to defend VFP as my choice against the 'Industry Standards'. The only reason I am still 'allowed' to use VFP for my application is that it would take to much time/resources to convert to Billy's pet language.
>>I'll get off the pulpit now...:)
>
>I'll listen to you when they add security features to VB's PRINT # command...until then, stop being troubled by having to purchase the same security featyres requored by every other product. If you like, you cna use MSDE with VFP.

Just expressing a wish, not to you specifically, nor am I troubled. If enough people express a need for it, it may become a reality in the future.
.. or so I'd like to think.