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
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