Re: Fox is dead, long live the fox!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



There are, apparently, some exciting new features coming in Orcas (the next
version of VS, after VS 2005)....and these features are based on Fox! See my
blog comments on this
http://www.craigberntson.com/archives/2005_06_08_archive.asp#111825002355535716

--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
www.foxcentral.net


"Ty Salistean" <tsaliste@xxxxxxxxx> wrote in message
news:ei7peVFbFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
>I am a FoxPro developer that has moved to C#. There are features in .NET
> that I like but I would like to voice my concern over the data aspect.
>
> ADO was very difficult to work with so M$ rewrote the engine and named it
> ADO.NET. I would like to say that it is not good either. The ability to
> manipulate data on the client side is a very nice feature. ADO.NET
> provides
> some tools for for this, but nothing like FoxPro. Let me give an example:
>
> I have an XML document that is received by a .NET web service. Behind the
> web service, I have a data object that processes the data and updates a
> SQL
> Server. One of the XML documents that I have has a denormalized set of
> data
> that represents a parent-child relationship. Basically, the data
> duplicates
> every parent record for each child record.
>
> So what I need to do is to normalize the data before updating the
> database.
> This is a simple SELECT DISTINCT in FoxPro. M$ has provided a solution
> for
> this (http://support.microsoft.com/default.aspx?scid=kb;en-us;326176) and
> I
> am using that.
>
> This solution only works for a DISTINCT list on 1 field. That works in my
> scenario but it may not in others. Here is my question: Why can't M$
> allow
> .NET developers to run ANSI standard SQL queries on ADO
> datatables/datasets
> (SELECT, INSERT, UPDATE, DELETE)?
>
> This will allow other developers to learn ANSI syntax and be able to
> utilize
> SQL Server without much learning curve. I bet there are people out there
> that have programmed in .NET but have NEVER written a SQL SELECT
> statement.
> That is scary!!
>
> The ability to requery data on the client is an essential tool for every
> developer, unless you never save your data. They do give you dataviews,
> but
> you cannot do a DISTINCT listing on those. They only give you the ability
> to order data (SET ORDER TO), filter data (SET FILTER TO), and some
> others...
>
> HEY M$ - WE NEED TO MANIPULATE DATA ON OTHER PLACES BEYOND STORED
> PROCEDURES!!!!!!! THAT IS KEY TO OUR JOB!!!!!
>
> I would only ask that M$ learn from its past mistakes: DAO, RDO, ADO, and
> I
> will add ADO.NET. I am sure that I am missing some. What is one thing
> that
> has remained constant in FoxPro for 10+ years (I only go back to FoxPro
> 2.5
> for DOS)? Data access...
>
> "Paul Pedersen" <no-reply@xxxxxxxx> wrote in message
> news:O8mFRZ5ZFHA.3224@xxxxxxxxxxxxxxxxxxxxxxx
>> "To help developers who currently use or plan to program on the .NET
>> platform, members of the Visual FoxPro team are also working on data
>> programming for the Microsoft .NET platform."
>>
>> We always knew that Fox's data handling was superior to anything else out
>> there, including dotnet.
>>
>> Although they say there are no plans to merge, a de facto merge could be
>> coming, if only because dotnet copies Fox's features.
>>
>>
>>
>
>


.



Relevant Pages

  • Re: Fox is dead, long live the fox!
    ... but nothing like FoxPro. ... ..NET developers to run ANSI standard SQL queries on ADO datatables/datasets ... if only because dotnet copies Fox's features. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Microfocus & Oracle data types
    ... Like you I am *NO* expert at SQL. ... Next one is me "Don't use Directives if you ... using features I'd forgotten I had included. ... So now I let the ESQL module generate my syntax - the text ...
    (comp.lang.cobol)
  • RE: Quality of FreeBSD
    ... FreeBSD development model typically addresses change at the tree HEAD, ... Probably it is no longer important to support chip ... > project schedule means, with long, long list of new features. ... I think you'll find many FreeBSD developers enjoy working on FreeBSD best ...
    (freebsd-stable)
  • Re: quota deadlock on 6.1-RC1
    ... many new features. ... there is never enough time to fix all the bugs. ... there are currently 5,424 PRs in the system (984 are ports PRs; ... developers who are willing to spend time working on them. ...
    (freebsd-stable)
  • Re: quota deadlock on 6.1-RC1
    ... The developers work for free. ... There are always tradeoffs between stability and features. ... to declaring 5.X "STABLE" until all the major bugs were fixed. ... absolute deadline) releases, with smaller feature sets, to enable smaller ...
    (freebsd-stable)