Which to buy?

Similar prices.

All I want to do is to rewrite some DOS-based Foxpro2 stuff for Windows.

---

Request for Question Clarification by hammer-ga on 27 Jun 2003 04:28 PDT

Do you know any programming languages other than FoxPro's?

Will you distribute this application to anyone else, or is it for your own use?

Do you own/use any other database products, such as Access, mySQL or SQLServer?

- Hammer

---

Clarification of Question by probonopublico-ga on 27 Jun 2003 10:06 PDT

Hi, Hammer

I know BASIC.

It's mainly for my own use.

I have Access (which I'm not crazy about).

I do want a Windows-based application ... Isn't mysql Linux?

Rgds

Bryan

---

Request for Question Clarification by hammer-ga on 27 Jun 2003 10:42 PDT

mySQL is offered for a many platforms, including Windows, but that's
not why I asked. In your case, I'd recommend Visual FoxPro (VFP) over
Visual Studio 6 (VS6). Here's why:

1. VFP already knows how to be a database engine. VS6 does not. You
can use VS6 to write a front-end for other database engines, but since
you don't have one that you like and are familiar with, that's quite a
learning curve. If you by VS6, you will also need a database back-end
to go with it. Depending on the package, VS6 may come with an engine,
such as MSDE or SQL Server, but it is still a separate product that
you would need to learn how to use and to hook your VS6-built forms
to. Microsoft includes a Data Environment and Data-Bound Controls to
ease this process, but many programmers (including me) find these
buggy and refuse to use them.

2. You already know how to program with FoxPro. I don't see a reason
for you to have to learn Visual Basic or Visual C++.

3. This application is only for your own use, so there is no real
reason not to stick with a product that you are already comfortable
with.
 

As I've already stated, I'm not a VFP expert. I don't know VFP's pros
and cons as a product, but, as a general statement, this would be my
recommendation.

- Hammer

---

Clarification of Question by probonopublico-ga on 27 Jun 2003 11:05 PDT

Hi, Hammer

Great! 

I like your thinking.

Please post as an answer.

KR

Bryan

Hi Bryan,

Posting the RFC as requested...

In your case, I'd recommend Visual FoxPro (VFP) over Visual Studio 6
(VS6). Here's why:
 
1. VFP already knows how to be a database engine. VS6 does not. You
can use VS6 to write a front-end for other database engines, but since
you don't have one that you like and are familiar with, that's quite a
learning curve. If you by VS6, you will also need a database back-end
to go with it. Depending on the package, VS6 may come with an engine,
such as MSDE or SQL Server, but it is still a separate product that
you would need to learn how to use and to hook your VS6-built forms
to. Microsoft includes a Data Environment and Data-Bound Controls to
ease this process, but many programmers (including me) find these
buggy and refuse to use them.
 
2. You already know how to program with FoxPro. I don't see a reason
for you to have to learn Visual Basic or Visual C++.
 
3. This application is only for your own use, so there is no real
reason not to stick with a product that you are already comfortable
with.
  
 
As I've already stated, I'm not a VFP expert. I don't know VFP's pros
and cons as a product, but, as a general statement, this would be my
recommendation.
 
- Hammer

---

Clarification of Answer by hammer-ga on 27 Jun 2003 11:31 PDT

BTW, as another option:

Visual Studio 6 Enterprise comes with Visual FoxPro 6. If the pricing
works out, you can get Visual Studio, then get Visual FoxPro 8 at the
upgrade price. If you have any interest in playing with any of the
other Visual Studio components, that might be the way to go.

Just a thought...

- Hammer

Brilliant!

Many thanks for the afterthought, too