VFoxpro or VBasic which one is better to develope database application. At
the moment I using the MS-Access for the creating db app.

Regards,

BP

It's your call!

Learn VFoxPro & you'll have a very good, stable, fast, scalable RDMS. If
you're going to have a lot of users & data then stay away from Access - it's
a 'desktop database'.

Otherwise, if you've been using VB already then try SQL Server - we've just
started using it & it's the dog's private parts!

Dave

Excuse me because I'm from Spain and my english is very bad.
VBasic is easier tehn VFox,but if you want a good an d secure program you
could use Fox,but VBasic isn't the worst and isn't the best.
Adios.

Please don't include CDMA in your troll!
peter walker

my 2 cents

Remember that VB is not a database.  I've developed databses in VB that
used Foxpro, Oracle, Essbase, SQL Server ... heck, even HTML files as
data sources.

Look at the needs of your organization and check the specs on Foxpro.
As far as VB, in general, it uses an Access back end for a file-based
database and SQL Server for a Client-Server Architecture.  If you want
to check out specs on these technologies, go to the microsoft site and
look up these as well as ADO, RDO and DAO (the database engines used to
access the data).

Sent via Deja.com http://www.deja.com/
Before you buy.

 it's the dog's private parts!??
What does that mean?

It's an approach to a latinan expression wich means something like "best of
the best".

To my mind, switching to VB from Access is much easier then to VFP.
And to my experience, the choise heavily depends on what type of DB
application should be developed: client-server or file-server based.

For client-server VB is better, for file server VFP gives better performance
and development speed.

Yuriy Shalak

If you're making the switch anyway (and you should -building a serious app
using Access forms and modules should be reserved for our Creator) why
move to another limiting environment.  VB is not a DB engine, but has great
hooks for almost any RDBMS you like (including Foxpro).  In some cases
I maintain a single piece of code for different desktop apps and web apps.
Migrating to different RBDMSs is usually very simple.
mp

I'll never understand why VB-Pros talks about VFP like if it was the "little
brother" of VB!. There are some facts that many VB developers seems to
unknow:

1. VFP is a desktop RDBMS itself with an extense and rich OOP programming
language; VB is easy and powerfull develop environment for external RDBMS.

2. All of the most important ways to access and manipulate data available
for VB (ADO, RDO, ODBC) can also be used within VFP. This means that the
same code you write in VB to run a query on a remote table will work also in
VFP.

3. VFP has a full native SQL language implementation: SELECT-SQL, DML, DDL;
VB has not.

4. VFP OOP implementation is far better than VBs. In fact, in VFP you can
subclass any native visual and non-visual control. The only way to do this
in VB is using ActiveX.

5. Almost any ActiveX control that can be used in VB can be also used in VFP

6. VFP apps is as fast as VB apps, and VFP string handle is faster than VBs.

7. VFP has an incredible collection of functions to process dates, strings,
numbers, objects, arrays; most of then aren't available in VB.

8. Report managment in VFP is far better than in VB and you do not need any
external software.

9. VFP is integrated with Internet as well as VB is. In fact, there are
native controls to jum to URLS, send an receive mails, etc. Plus, you can
instantiate an MS Explorer window in for your form.

10. And the most important point, something that VB programmers can only
dream about: VFP supports macro-substitution, wich means that you are able
to run dynamicaly-generated code in runtime. In fact, you can run commands,
create forms, class libraries and reports on-the-fly!

Victor Espina

VB is not a database.  It can access databases (SQL,
Oracle,MSDE,Access, VFP.....) though ODBC, ADO, RDO ,DAO or OLE DB.  If
you develop a database app in VB you still need the backend.  Visual
FoxPro is a Database application.  It uses it's own extremely fast and
versatile data engine or it can access other databases using the same
technology as VB.

You need to ask your self how much data am I storing?
How data security do I need?
How much do I want to spend?
Is this a 7/24 app?

VFP databases are wide open.  There is no built in security like in SQL
server.  VFP has not runtime distributions Costs.  There is no limit or
user count built into the product.  SQL server you must buy licenses
for each user (connection) of the database. (Building a Middletier to
access the database will cut the number of licenses need but adds other
costs).  VFP supports single tables to 2 Gig and a database container
to 2 gig.  Sql Server does not have that limit.  VFP tables need
maintenance like SQL server tables, but VFP tables cannot be accessed
while or open by anything other than the app performing maintenance
while maintenance is occuring.  Therefore, you must have scheduled down
time.

VB builds smaller apps with better integration with most ActiveX
controls.  VFP has greater data manipulation capabilities whether local
tables or another backend is used.

Hope this helps.

Sent via Deja.com http://www.deja.com/
Before you buy.

Almost correct. In VB 6.0 there is good enough database development tools.

... and barely needs. It (VB) just exploits different approach.

In VB you can use custom controls (written in VB). Moreover, these controls
can
have custom events. In VFP subclassed controls cannot extend the event list
of
base control. This is one of very unpleasant feature of VFP.

VFP

"Almost" is a good word here. Winsock.ocx definitely does NOT work in VFP.

VBs.

But VB RAD (Intellisense, etc.) makes code writing much faster in VB.

That's correct.

Again _was_ true up to VB 6.0. Currently it is not.

But, for example, you can use VB message box while you application
works as [OLE] Autometion server and VFP can supply only "under the hood"
operations in this mode.

Well, actually, this is not needed very often (to my experience).

And you forget the following:

11. VFP is less OLE-oriented and in desktop mode requires simple copying
of the application files and several run-time dlls to work. VB application
requires
installation.

Yuriy Shalak