访问或FoxPro？ [英] Access or FoxPro?

问题描述

我是数据库的新手，我不确定使用哪个DBMS。我有一个非常简单的数据库整体知识。我非常感谢
感谢（简化）消息，解释了两个程序的优点和

的缺点。


非常感谢


Simon

I am a newcomer to databases and am not sure which DBMS to use. I have
a very simplified knowledge of databases overall. I would very much
appreciate a (simplifed) message explaining the advantages and
disadvantages of both programs.

Many Thanks

Simon

推荐答案

我会说，因为你在ms-access新闻组中提出问题，

那么你不得不期待一些人倾向于使用ms-access。


另一个问题是你有多少以前的开发经验。如果你做了很多编码，并且更喜欢OO方法进行应用程序开发，那么

你当然可以找到FoxPro你的一杯茶。

如果你花费大量时间用VB这样的语言进行编码，那么你会发现

ms-access更容易学习。 （事实上​​，你将使用编程语言
用于在ms-access中编写代码与VB实际上是一样的，但是表格是不同的b $ b。）


关于FoxPro唯一真正的垮台是没有那么大的b $ b b用户群，而且还有更多的书籍，网站和新闻组。 />
ms-access。


此外，你还意识到像ms-access这样的产品不再是一个真正的数据库系统了。 ms-access是一个前端工具，可让您开发

报表，表单和编写代码。数据库引擎是一个单独的问题。

当你购买像Oracle或sql-server这样的数据库系统时，你只能得到一个允许你存储数据的盒子。您仍然需要使用某些工具编写应用程序和

用户界面。这些工具可以是一个Web界面，

或VB甚至是ms-access。


因此，应该记住数据库系统之间的分离，或者

所谓的数据库引擎，以及你使用的应用程序开发工具。


因此，应该将ms-access视为应用程序开发工具，而不是一个

数据库。实际上，办公室CD配有两个数据库引擎。您可以选择使用ms-access的数据库引擎。


ms-access或FoxPro都可以成为可以连接到

您选择的数据库引擎。


微软已经向开发人员推出了更多的FoxPro环境，并且已经向市场推出了更多的产品。终端用户。因此，ms-access被认为更容易学习。


FoxPro在最终应用程序的分发方面也有一些优势。

但是，如果您使用第三方工具进行
ms-access，那么这些优势并不是那么好。许多人会争辩说，在一个文件中，msPro访问的JET引擎比用于
共享（或者每个FoxPro）的文件共享中的FoxPro数据库引擎更可靠开发人员我知道已经遭受某种形式的

索引损坏。


所以，如果你需要一个Object的应用程序开发平台
一直定位，然后FoxPro可能是你的票。如果你需要

的东西可以让你的运行速度更快，那么Ms-access就可以了。

可能是最佳选择。


很多将取决于您以前的编程经验。如果你没有
有很多开发经验，那么我会打赌ms-access。


但是，不要算ms - 作为一个严谨的开发工具也可以。你

可以创建类对象，你在ms访问中尝试的任何项目仍然需要详细计划。


这是我的一篇文章，关于使用类对象给你和想法

我的意思：

http://www.attcanada.net/%7ekallal.m.../WhyClass.html

另外，这里有关于我在ms-access中做过的项目的一些注释，你可能会再次

找到一个很好的阅读：

<一个rel =nofollowhref =http://www.attcanada.net/%7ekallal.msn/Articles/fog0000000003.html\"target =_ blank> http://www.attcanada.net/%7ekallal.m .. .000000003.html


-

Albert D. Kallal（MVP）

加拿大艾伯塔省埃德蒙顿
ka****@msn.com
http://www.attcanada.net/~kallal.msn

I would have say that since you asked the question in a ms-access newsgroup,
then you kind of have to expect some leaning towards using ms-access.

The other issue is how much previous development experience you have. If you
done a lot coding, and prefer a OO approach to application development, then
you certainly might find FoxPro your cup of tea.

If you spend a lot of time coding in a language like VB, then you will find
ms-access a lot easier to learn. (in fact, the programming language you will
use to write code in ms-access is really the same as VB, but the forms are
different).

About the only real downfall of FoxPro is that there is not as large of a
user base, and there are more books, web sites, and newsgroups for
ms-access.

Further, you also realize that products like ms-access are not really a
database system anymore. ms-access is a front end tool that lets you develop
reports, forms, and write code. The database engine is a separate issue.
When you purchase a database system like Oracle, or sql-server, you only get
a box that lets you store data. You still have to write the application and
the user interface using some tools. Those tools could be a web interface,
or VB or even ms-access.

Thus, one should keep in mind the separation between the database system, or
so called database engine, and the application development tools you use.

Thus, one should view ms-access as a application development tool, and not a
database. In fact, the office cd ships with two database engines. You can
choose to use either database engine with ms-access.

Both ms-access or FoxPro make good development tools that can connect to
your database engine of choice.

Microsoft has marketed the FoxPro environment more to developers, and
ms-access has been marketed more towards end users. Thus, ms-access is
considered easier to learn.

FoxPro also has some advantages in distribution of the final application.
However, those advantages are not that great if you use 3rd party tools for
ms-access. Many people will argue that the database engine for FoxPro in a
file share is more reliable then the JET engine for ms-access in a file
share (however, every FoxPro developer I know has suffered some form of
index corruption).

So, if you are in need of a application development platform that is Object
Orientated all the way, then FoxPro might be your ticket. If you need
something that will get you up and running a lot faster, then Ms-access is
probably the way to go.

Much will depending on your previous programming experience. If you don''t
have a lot of development experience, then I would bet on ms-access.

However, don''t count ms-access out as a serous development tool either. You
can create class objects, and any project you attempt in ms-access still
should be planned in detail.

Here is a article of mine on using class objects to give you and idea of
what I mean:

http://www.attcanada.net/%7ekallal.m.../WhyClass.html
Also, here is some notes on a project I did in ms-access, you might again
find this a good read:

http://www.attcanada.net/%7ekallal.m...000000003.html

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

我远不是Access或Foxpro的专家。我在Dbase，Foxbase和Foxpro 2.6中做了很多

编程。我已经使用Access几年了，但是最近才开始开发。


我可能只是不知道如何在Access中做到这一点，但我错过了我在Foxpro中运行个人记录的工具

：


在Foxpro中你可以编写一个循环来跳过（随机）通过每条记录在一个

表中并对各个记录执行操作（即计算一个运行的总计
）。在Access中，您可以作为一个组对记录进行操作。


Foxpro分散/聚集命令是屏幕在

变量上操作的快捷方式，而不是直接在实时数据。


Foxpro记录在删除时不会消失，直到你收拾好桌子。


我发现总有办法做我需要的东西在Access中，以及对网站的大量帮助。我会说，至少对我的知识水平来说，Access似乎有更多精巧的方式来做Foxpro，你可以通过这个方式来支持你。

。 br />

我的两分钱价值

比尔。

I am far from being an expert in either Access or Foxpro. I did a lot of
programming in Dbase, Foxbase and Foxpro 2.6. I have used Access for several
years, but just recently started development.

I probably just don''t know how to do it in Access yet, but I miss the tools
I had in Foxpro to operate on individual records:

In Foxpro you can program a loop to skip (randomly) through each record in a
table and perform operations on individual records (ie calculate a running
total). In Access you operate on records as a group.

The Foxpro scatter/gather commands are quick ways for a screen to operate on
variables rather then directly on live data.

Foxpro records when deleted are not gone until you pack the table.

I find there are always to do things I need in Access, and plenty of help on
the web. I would say, at least for my level of knowledge, Access seems to
have more of a finesse way of doing things where Foxpro you can power your
way through.

My two cents worth
Bill.

到很多垃圾邮件列表这里.com（BillB）写道：

< vp ************ @ corp.supernews.com>：

to much SPAM to list here.com (BillB) wrote in
<vp************@corp.supernews.com>:

我可能只是不知道如何在Access中做到这一点，但我想念我在Foxpro中使用的工具来处理各个记录：

在Foxpro中你可以编写一个循环跳过（随机）通过表中的每个
记录并对各个记录执行操作（即
计算运行总计）。在Access中，您可以将记录作为
组进行操作。


SQL更新查询有些事情无法完成。

并且运行总计可能不属于存储在表，在

任何事件！


为了顺序逐步浏览Access中的记录，你会想要

记录集。如果您将数据存储在MDB文件中，

使用DAO。如果您使用SQL Server作为数据，ADO将会更有用。
可能更有用。两者都有Recordset对象，虽然它们没有相同的属性和方法。

Foxpro分散/收集命令是屏幕快速的方式
操作变量而不是直接操作实时数据。


听起来像Access中的未绑定表单。


访问肯定会对绑定数据产生偏见。这是一件很好的事情，大部分时间都是好事。如果你需要解决它的问题，那么它会变得更加复杂。

Foxpro记录在删除之前不会消失，直到你打包表。


我见过dBase应用程序，其中有人使用DELETE过滤

记录用于某种目的，然后没有取消删除它们。

他们逐渐从他们的数据库中丢失了越来越多的数据。

直到几年后才发现它。


我没有任何优势可以获得这种能力 - 如果记录

应该被删除，它应该被删除。


当然，在大多数情况下应用程序，实际上删除记录的地方并不多，因为如果你的记录与其他表格中的

记录有关，你可能需要保留

用于维护与其他数据的关系的记录。因为

，大多数时候你不想真正删除

记录，你只想要一个标志字段，表明

记录已经退役。然后你过滤掉那些来自

你的活动数据集的记录。


实际上，这可能非常复杂，因为对于某些任务你可以

用于显示已删除的记录，而在其他人中则不是。


这不是一个小问题。

我发现总有在Access中做我需要的东西，并在网上提供大量的帮助。我会说，至少对于我的知识水平，Access似乎有更多精巧的方式来做你可以通过Foxpro驱动的东西。

I probably just don''t know how to do it in Access yet, but I miss
the tools I had in Foxpro to operate on individual records:

In Foxpro you can program a loop to skip (randomly) through each
record in a table and perform operations on individual records (ie
calculate a running total). In Access you operate on records as a
group.
There are some things that can''t be done with a SQL update query.
And a running total probably doesn''t belong stored in a table, in
any event!

For sequentially stepping through records in Access, you''ll want to
look into recordsets. If you''re storing your data in an MDB file,
use DAO. If you''re using SQL Server for your data, ADO will
probably be more useful. Both have Recordset objects, though they
don''t have the same properties and methods.
The Foxpro scatter/gather commands are quick ways for a screen to
operate on variables rather then directly on live data.
Sounds like an unbound form in Access.

Access is definitely prejudiced towards bound data. And that''s a
good thing, most of the time. When you need to work around it''s
problems, then it becomes more complex.
Foxpro records when deleted are not gone until you pack the table.
I''ve seen dBase applications where someone used a DELETE to filter
the records for a certain purpose, and then didn''t undelete them.
They gradually lost more and more data from their database and
didn''t discover it until years later.

I don''t see any advantage to having that capability -- if a record
should be deleted, it should be deleted.

Of course, in most applications, there''s not much place for
actually deleting records, because if you''re records are related to
records in other tables, you likely need to keep the record for the
purpose of maintaining its relationships with other data. Because
of that, most of the time you don''t want to actually delete
records, you just want to have a flag field that indicates that the
record has been "retired." Then you filter out those records from
your active data sets.

It can be very complex, actually, because for some tasks you may
wat the deleted records to show, and in others you don''t.

Not a trivial subject.
I find there are always to do things I need in Access, and plenty
of help on the web. I would say, at least for my level of
knowledge, Access seems to have more of a finesse way of doing
things where Foxpro you can power your way through.

对我来说听起来像Access强制你做对了，而FoxPro

允许你克服你的方式看似有效的结果。

-

David W. Fenton http： //www.bway.net/~dfenton

dfenton at bway dot net http://www.bway.net/~dfassoc

Sounds to me like Access forces you to do it right, whereas FoxPro
allowed you to kludge your way to a result that seemed to work.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

这篇关于访问或FoxPro？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！