difference between Fox pro and MS Access? 
Author Message
 difference between Fox pro and MS Access?
hello

Please, if anybody is firmilar with both FOX Pro and MS Access, tell me a
little about both programs and it's pros. and cons.

greatly appreciated

Johnny Wang




Sat, 25 Aug 2001 03:00:00 GMT
 difference between Fox pro and MS Access?

Let's be careful here because there is a HUGE difference betwen FoxPro and
Visual FoxPro.  Visual FoxPro has a much better windows interface than FoxPro
and you can do a lot more but the learning curve is much steeper.  My
understanding is that Access is definitely a lot slower once you have more than
4-6 users or so on a network.  It's not a database from the ground up like VFP
or FoxPro is.
Mike


Sat, 25 Aug 2001 03:00:00 GMT
 difference between Fox pro and MS Access?
Access is an end-user tool. It is sold with Office, and end-user product. It
is designed for small applications with small number of records and users.
Visual FoxPro is a developer tool. It is sold with Visual Studio, a
developer product. It is designed for small to large applications, can
handle millions of records and hundreds of users with ease.

--

Craig Berntson
Microsoft Visual FoxPro MVP
Salt Lake City Fox User Group
http://www.xmission.com/~craigb


Quote:
>hello

>Please, if anybody is firmilar with both FOX Pro and MS Access, tell me a
>little about both programs and it's pros. and cons.

>greatly appreciated

>Johnny Wang





Sat, 25 Aug 2001 03:00:00 GMT
 difference between Fox pro and MS Access?
My opinion:

Access is slow. VFP is fast.

Access puts everything into a file.  When there's something wrong,
everything will be gone.
VFP does not put everything into a file (if I don't use database), therefore
I can create many projects sharing the same files (tables, reports, screens,
PRGs, class libraries, whatever).

Access basic is cryptic. (What the hell is "Bookmark"?  Why don't support
"record number"?)
VFP is straight forward (A table is just an array of records, one by one and
each one has a record number).

Writing access basic requires lots of typing (Set ABC = efg.xyz.abc...set
def = abc.def.kkk... set xyz = def.ijk.lmn)
Writing VFP is a lot better (use mytable)

Access is designed by Microsoft (poorer design; I can still remember the
time when Microsoft's "Quick" Basic is defeated hands down by Borland's
tools)
VFP is "bought" by Microsoft (Aha, not designed by Microsoft. I have some
confidence)

Brian.

Quote:

>hello

>Please, if anybody is firmilar with both FOX Pro and MS Access, tell me a
>little about both programs and it's pros. and cons.

>greatly appreciated

>Johnny Wang





Sun, 26 Aug 2001 03:00:00 GMT
 difference between Fox pro and MS Access?
Brian
When you add a table to a Visual FoxPro database it doesn't get physically
copied into a database. It's still a separate DBF-file on your harddisk. The
database is a system table with information about the tables, views,
connections, stored procedures and so on that you've combined. The DBF table
file has the name and path of the database it belongs to recorded in its
header. This backlink is the only difference between a free table and a
database table.
-Anders

Quote:

>My opinion:

>Access is slow. VFP is fast.

>Access puts everything into a file.  When there's something wrong,
>everything will be gone.
>VFP does not put everything into a file (if I don't use database),
therefore
>I can create many projects sharing the same files (tables, reports,
screens,
>PRGs, class libraries, whatever).

>Access basic is cryptic. (What the hell is "Bookmark"?  Why don't support
>"record number"?)
>VFP is straight forward (A table is just an array of records, one by one
and
>each one has a record number).

>Writing access basic requires lots of typing (Set ABC = efg.xyz.abc...set
>def = abc.def.kkk... set xyz = def.ijk.lmn)
>Writing VFP is a lot better (use mytable)

>Access is designed by Microsoft (poorer design; I can still remember the
>time when Microsoft's "Quick" Basic is defeated hands down by Borland's
>tools)
>VFP is "bought" by Microsoft (Aha, not designed by Microsoft. I have some
>confidence)

>Brian.


>>hello

>>Please, if anybody is firmilar with both FOX Pro and MS Access, tell me a
>>little about both programs and it's pros. and cons.

>>greatly appreciated

>>Johnny Wang





Sun, 26 Aug 2001 03:00:00 GMT
 difference between Fox pro and MS Access?
The backlink path from the table to the DBC that it is
in is a relative path, by the way.  I've seen concern
from some people about the recording of paths in VFP.
Since they are relative paths, there is not a location
dependence as some have feared.  The only requirement
regarding tables in a DBC is that they are in the
same location relative to the DBC, i.e. in the same
directory or in the directory above, below, whatever.
Most developers place the DBC in the same folder as
the the tables that it contains.  This is probably
the safest method since the "paths" to the tables
and the backlinks to the DBC are effectively gone.
So the DBC and the tables can be placed in any
directory and still function correctly.

-- TRW

Quote:

> Brian
> When you add a table to a Visual FoxPro database it doesn't get physically
> copied into a database. It's still a separate DBF-file on your harddisk. The
> database is a system table with information about the tables, views,
> connections, stored procedures and so on that you've combined. The DBF table
> file has the name and path of the database it belongs to recorded in its
> header. This backlink is the only difference between a free table and a
> database table.
> -Anders


> >My opinion:

> >Access is slow. VFP is fast.

> >Access puts everything into a file.  When there's something wrong,
> >everything will be gone.
> >VFP does not put everything into a file (if I don't use database),
> therefore
> >I can create many projects sharing the same files (tables, reports,
> screens,
> >PRGs, class libraries, whatever).

> >Access basic is cryptic. (What the hell is "Bookmark"?  Why don't support
> >"record number"?)
> >VFP is straight forward (A table is just an array of records, one by one
> and
> >each one has a record number).

> >Writing access basic requires lots of typing (Set ABC = efg.xyz.abc...set
> >def = abc.def.kkk... set xyz = def.ijk.lmn)
> >Writing VFP is a lot better (use mytable)

> >Access is designed by Microsoft (poorer design; I can still remember the
> >time when Microsoft's "Quick" Basic is defeated hands down by Borland's
> >tools)
> >VFP is "bought" by Microsoft (Aha, not designed by Microsoft. I have some
> >confidence)

> >Brian.


> >>hello

> >>Please, if anybody is firmilar with both FOX Pro and MS Access, tell me a
> >>little about both programs and it's pros. and cons.

> >>greatly appreciated

> >>Johnny Wang





Sun, 26 Aug 2001 03:00:00 GMT
 
 [ 8 post ] 

 Relevant Pages 

1. About MS SQL ACCESS FOX PRO SERVLETS

2. MS ACCESS & FOX PRO

3. Visual Fox Pro vs MS Access

4. MS ACCESS & FOX PRO

5. US-NC-Access Programmer, (Access 2.0 and 7.0, SQL Server, Fox Pro), DB Basics, Inc.#381

6. difference of SQL statement between MS Access and MS SQL server

7. MS Visual Fox Pro (Personal Opinion Poll)

8. mails: ms fox pro to outlook

9. Fox Pro ? using MS dbase driver

10. FILE MAKER Pro Compatibility with MS ACCESS, MS EXCEL

11. FILE MAKER Pro Compatibility with MS ACCESS, MS EXCEL

12. FILE MAKER Pro Compatibility with MS ACCESS, MS EXCEL


 
Powered by phpBB® Forum Software