Re: SQL Server vs. Foxpro

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Wayne Snyder (wayne.nospam.snyder_at_mariner-usa.com)
Date: 06/15/04 

Date: Tue, 15 Jun 2004 08:04:59 -0400

I used to use Foxpro for (relatively) small apps, and it ran quite well...
( Like any product, it had its foibles.) But it ran better that I expected
for smallish data sets...

SQL Server will scale better.
There are many more tools available which can use data in SQL Server
(reporting tools, dev tools, etc.)
Although MS has been saying for years that each new release will be the last
for Foxpro, it's highly loyal users have prevented MS from making good on
it's promise... One day tho, it will be the end.. 

-- 
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark" <maxmann@kc.rr.com> wrote in message
news:OryWB5nUEHA.1152@TK2MSFTNGP09.phx.gbl...
> Okay, I know that SQL Server is on a different level than foxpro, but I
have
> a feeling I'm going to need to PROVE that this is the case to some people.
>
> My company has recently "merged" with another company who uses Foxpro as
the
> backend for their ASP front end.
>
> We currently use SQL server 2000 and have an ASP/ASP.NET front end.  Their
> data and our data (in combination) is going to need to be made available
to
> their application and our application.
>
> Long term, I see the best solution being all of the data in a SQL Server
> backend.  Another solution proposed has been a regularly scheduled "merge"
> of the data (push/pull) from both backends, which sounds like a nightmare
> waiting to happen.
>
> Can anyone point me toward any good references or sites or even personal
> experience on what they would recommend in this situation.  I understand
you
> don't have all the details, but some direction on this would be great.  I
> myself know very little about foxpro, but it sounds comparable to MS
Access.
>
> thanks a lot.
>
>

Relevant Pages

  • Re: data provider
    ... using the foxpro OLEDB route does the end user have to have Sql Express ... There are two ways to procede to get VFP data into SQL Server Compact ... these are the OleDb data providers: ...
    (microsoft.public.sqlserver.ce)
  • SQL Server vs. Foxpro
    ... Okay, I know that SQL Server is on a different level than foxpro, but I have ... a feeling I'm going to need to PROVE that this is the case to some people. ... backend for their ASP front end. ... We currently use SQL server 2000 and have an ASP/ASP.NET front end. ...
    (microsoft.public.sqlserver.server)
  • Re: data provider
    ... provider that your Foxpro app will use. ... When I talk about a sdf file in my mind its a SQL Server Compact edition ... create a SSCE database that contains all of my tables ...
    (microsoft.public.sqlserver.ce)
  • Re: help with conection between SQL server & DBF file with cdx index. thanks
    ... To move the data into sql server, you likely don't want, or need to use ... consider at least linking to the Foxpro tables, ... Originally posted by Cindy Winegarden Microsoft Visual FoxPro MVP: ... Start with the latest ODBC driver for FoxPro and Visual FoxPro, ...
    (microsoft.public.access.externaldata)
  • Re: data provider
    ... provider that your Foxpro app will use. ... When I talk about a sdf file in my mind its a SQL Server Compact edition ...
    (microsoft.public.sqlserver.ce)