ADP ......另一种观点 [英] ADPs ... another view
问题描述
我已经在Ac2K和AcXP中开发了三年的ADP。我已经出售了
两个ADP应用程序> 30,000美元，一个到亚特兰大的一家大公司，
，一个到当地（加拿大安大略省）的学校董事会，还有许多小的
。
最初我的应用程序已经开始通过
互联网访问MS-SQL Server。出于开发目的，我使用MSDE，或者从我的网站提供商处租用SQL Server DB
，每月15美元。 学校董事会应用程序
上面的
正在恢复使用Board的SQL服务器，而不是内部网的
。这是一项有计划的变更，是为了遵守他们的政策，而不是任何表现或已知的安全问题。
我没有遇到任何问题ADP的主要问题。有三个
问题我在短时间内发现令人费解：
1.我无法让子表单正确链接;我现在可以了，但是我不能用b $ b来解释我正在做什么新的，或者不同的（顺便说一句，我开始
链接我自己的子表格并发现这是简单而有力的）;
2.我无法在运行时过滤报告的记录来源;在MS的'
ADP新闻组中，有人指出报告的输入参数可以
设置为表单控件的值，或者是公共功能，这完全解决了这个问题;
3.我发现ADP似乎对正确安装MDAC非常敏感
（特别是ADO）。如果它不是A-1，它们会崩溃，并且错误消息
不是那么有用，而且AFAIK没有记录。找到MS的Comcheck工具
允许我检查并验证问题是什么，但这仍然让我感到麻烦，因为我发现IT部门可能会松懈这些
安装。
通常我的应用程序有数百个存储过程，而且只有几个小的VBA模块。我的VBA通常只为SPROC提供参数。我已经了解了VIEWS的功能有多强大，而且我特别印象
更新它们;也就是说，可以更新以某种特定方式编写脚本的VIEW，这会更新VIEW的一个源表。我还要注意，人们可以使用VIEW作为SPROC的来源，将
的过滤与另一个的即时过滤结合起来。
虽然我没有使用太多VBA，但在学校董事会申请表中我有一个
时间表。由于它考虑了许多可能的解决方案（在某些情况下是因素），因此它非常密集，为此我使用VBA，更喜欢
不要浪费太多服务器CPU（SPROC解决方案），当我可以
在许多客户机（VBA解决方案）中分配消耗。对于
时间表，我使用批量更新。迄今为止，这些成千上万的更新
并未导致任何问题或错误。 VBA解决方案和SPROC
解决方案大致需要同样的时间来完成同样的事情。顺便说一下，你知道吗？b
$ b b b b b b b b b b b a a a a a a a a a a a a a a a a a
我无法告诉其他人是否使用MDB或ADP。
我从未使用过ODBC。我本质上是一个问题解决者，并且非常强迫
关于代码。我更喜欢一个对我来说做得少的平台，而不是一个对b $ b $做得更多的平台。我在ADP中开发而不是在MDB中开发，并且可能不会在MDB工作中使用
，即使它非常有利可图。我认为ADP在概念和实现方面都比MDB更先进。
我写这篇文章指出至少有一个开发人员，（我），是否承诺并且成功使用ADP，并且在使用它们时发现没有无法解决的问题。他已经出售了ADP应用程序，看起来他的客户很满意。
自从DBaseIII出版以来，我一直在使用数据库，大约1983年/>
（我想）。我已经通过FoxBase，FoxPro，Clipper和...进行了进展。
访问。 Clipper可能会为我留下最有用的p-coding
语言，但我确实喜欢ADP。
对不起如果你觉得我应该把它附加到这个主题的当前主题之一。
。我觉得我不能这样做，而不会与其他人所说的或与他们对抗的事情相矛盾。我根据自己的经验，只想表达我的意见。这是ADP
很棒。
-
Lyle
（对于e-邮件参考 http://ffdba.com/contacts.htm ）
I have developed ADPs now for three years, in Ac2K and AcXP. I have sold
two ADP applications for > $30,000 USD, one to a large company in Atlanta,
and one to a local (Ontario, Canada) school board, and numerous smaller
ones.
Initially my applications have started as accessing MS-SQL Server over the
internet. For development purposes I use MSDE, or rent an SQL Server DB
from my site provider for $15 USD monthly. The "school board" application
above is in the process of reverting to using the Board''s SQL server over
their intranet. This was a planned change and is in place to comply with
their policies, and not for any performance or known security issue.
I have not experienced any major problems with ADPs. There were three
issues which I found puzzling for a brief time:
1. I could not get sub forms to link properly; I can now, but I cannot
explain what I am doing new, or differently (incidentally, I started
linking my own "sub forms" and found this to be simple and powerful);
2. I could not filter the record source for a report at run time; in MS''s
ADP newsgroup, someone pointed out that a report''s Input Parameters could
be set to a form control''s value, or to a public function, and that solved
that problem completely;
3. I found that ADPs seem very sensitive to the proper installation of MDAC
(specifically ADO). If it?s not A-1 they crash, with an error message which
is not so helpful, and, AFAIK, undocumented. Finding MS''s Comcheck utility
allowed me to check and verify what the problem was, but this still
troubles me, as I find that IT departments can be lax about these
installations.
Typically my applications have hundreds of stored procedures, and only a
few small VBA modules. Often my VBA provides parameters for SPROCs only. I
have learned just how powerful VIEWS can be, and I am especially impressed
with updating them; that is one can update a VIEW which is scripted in some
particular way, and this updates one of the source tables for the VIEW. I
also note that one can use a VIEW as the source for a SPROC, combining the
filtering of the one, with the immediacy of the other.
Although I don''t use much VBA, in the school board application I have a
time tabling segment. As it looks at many possible solutions (factorials in
some cases) it is very code intensive, and for this I use VBA, preferring
not to have so much drain on the Server CPU (SPROC solution), when I can
distribute that drain among many client machines (VBA solution). For the
time tabling, I use batch updates. To date, these many thousands of updates
have not resulted in any problems or errors. The VBA solution and the SPROC
solution take about the same time to do the same thing. BTW, do you know
that one can largely duplicate one''s VBA code in SPROCS because one has
IFS, CASE and LOOPS available, variables, and UDFs there?
I could not advise anyone else about whether or not to use MDBs, or ADPs.
I''ve never used ODBC. I am by nature a problem solver, and quite compulsive
about code. I prefer a platform that does less for me, rather than one that
does more. I develop in ADPs and not in MDBs, and probably would not take
on an MDB job, even if it were quite lucrative. I think that ADPs are very
much advanced over MDBs in both concept and realization.
I write this to point out that at least one developer, (me), is both
committed to, and successful with ADPs, and has found no unsolvable
problems in working with them. He has sold ADP applications, and it seems
his clients are happy.
I have been working with databases since the time of DBaseIII, about 1983
(I think). I have progressed through FoxBase, FoxPro, Clipper and ...
Access. Clipper is likely to remain for me the most useful p-coding
language with which I have ever dealt, but I do like ADPs.
I am sorry if you feel that I should have attached this to one of the
current threads on this subject. I feel that I could not have done so
without contradicting what others have said, or confronting them. And I
simply wish to state my views, based on my experience. It is that ADPs are
great.
--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)
推荐答案
30,000美元，一个到亚特兰大的一家大公司，
和一个到当地（加拿大安大略省）的学校董事会，和许多较小的
。
最初我的应用程序已经开始通过
互联网访问MS-SQL Server。出于开发目的，我使用MSDE，或从我的网站提供商处租用SQL Server DB
30,000 USD, one to a large company in Atlanta,
and one to a local (Ontario, Canada) school board, and numerous smaller
ones.
Initially my applications have started as accessing MS-SQL Server over the
internet. For development purposes I use MSDE, or rent an SQL Server DB
from my site provider for
每月15美元。 学校董事会应用程序
上面的
正在恢复使用Board的SQL服务器，而不是内部网的
。这是一项有计划的变更，是为了遵守他们的政策，而不是任何表现或已知的安全问题。
我没有遇到任何问题ADP的主要问题。有三个
问题我在短时间内发现令人费解：
1.我无法让子表单正确链接;我现在可以了，但是我不能用b $ b来解释我正在做什么新的，或者不同的（顺便说一句，我开始
链接我自己的子表格并发现这是简单而有力的）;
2.我无法在运行时过滤报告的记录来源;在MS的'
ADP新闻组中，有人指出报告的输入参数可以
设置为表单控件的值，或者是公共功能，这完全解决了这个问题;
3.我发现ADP似乎对正确安装MDAC非常敏感
（特别是ADO）。如果它不是A-1，它们会崩溃，并且错误消息
不是那么有用，而且AFAIK没有记录。找到MS的Comcheck工具
允许我检查并验证问题是什么，但这仍然让我感到麻烦，因为我发现IT部门可能会松懈这些
安装。
通常我的应用程序有数百个存储过程，而且只有几个小的VBA模块。我的VBA通常只为SPROC提供参数。我已经了解了VIEWS的功能有多强大，而且我特别印象
更新它们;也就是说，可以更新以某种特定方式编写脚本的VIEW，这会更新VIEW的一个源表。我还要注意，人们可以使用VIEW作为SPROC的来源，将
的过滤与另一个的即时过滤结合起来。
虽然我没有使用太多VBA，但在学校董事会申请表中我有一个
时间表。由于它考虑了许多可能的解决方案（在某些情况下是因素），因此它非常密集，为此我使用VBA，更喜欢
不要浪费太多服务器CPU（SPROC解决方案），当我可以
在许多客户机（VBA解决方案）中分配消耗。对于
时间表，我使用批量更新。迄今为止，这些成千上万的更新
并未导致任何问题或错误。 VBA解决方案和SPROC
解决方案大致需要同样的时间来完成同样的事情。顺便说一下，你知道吗？b
$ b b b b b b b b b b b a a a a a a a a a a a a a a a a a
我无法告诉其他人是否使用MDB或ADP。
我从未使用过ODBC。我本质上是一个问题解决者，并且非常强迫
关于代码。我更喜欢一个对我来说做得少的平台，而不是一个对b $ b $做得更多的平台。我在ADP中开发而不是在MDB中开发，并且可能不会在MDB工作中使用
，即使它非常有利可图。我认为ADP在概念和实现方面都比MDB更先进。
我写这篇文章指出至少有一个开发人员，（我），是否承诺并且成功使用ADP，并且在使用它们时发现没有无法解决的问题。他已经出售了ADP应用程序，看起来他的客户很满意。
自从DBaseIII出版以来，我一直在使用数据库，大约1983年/>
（我想）。我已经通过FoxBase，FoxPro，Clipper和...进行了进展。
访问。 Clipper可能会为我留下最有用的p-coding
语言，但我确实喜欢ADP。
对不起如果你觉得我应该把它附加到这个主题的当前主题之一。
。我觉得我不能这样做，而不会与其他人所说的或与他们对抗的事情相矛盾。我根据自己的经验，只想表达我的意见。这是ADP
很棒。
-
Lyle
（对于e-邮件参考 http://ffdba.com/contacts.htm ）
15 USD monthly. The "school board" application
above is in the process of reverting to using the Board''s SQL server over
their intranet. This was a planned change and is in place to comply with
their policies, and not for any performance or known security issue.
I have not experienced any major problems with ADPs. There were three
issues which I found puzzling for a brief time:
1. I could not get sub forms to link properly; I can now, but I cannot
explain what I am doing new, or differently (incidentally, I started
linking my own "sub forms" and found this to be simple and powerful);
2. I could not filter the record source for a report at run time; in MS''s
ADP newsgroup, someone pointed out that a report''s Input Parameters could
be set to a form control''s value, or to a public function, and that solved
that problem completely;
3. I found that ADPs seem very sensitive to the proper installation of MDAC
(specifically ADO). If it?s not A-1 they crash, with an error message which
is not so helpful, and, AFAIK, undocumented. Finding MS''s Comcheck utility
allowed me to check and verify what the problem was, but this still
troubles me, as I find that IT departments can be lax about these
installations.
Typically my applications have hundreds of stored procedures, and only a
few small VBA modules. Often my VBA provides parameters for SPROCs only. I
have learned just how powerful VIEWS can be, and I am especially impressed
with updating them; that is one can update a VIEW which is scripted in some
particular way, and this updates one of the source tables for the VIEW. I
also note that one can use a VIEW as the source for a SPROC, combining the
filtering of the one, with the immediacy of the other.
Although I don''t use much VBA, in the school board application I have a
time tabling segment. As it looks at many possible solutions (factorials in
some cases) it is very code intensive, and for this I use VBA, preferring
not to have so much drain on the Server CPU (SPROC solution), when I can
distribute that drain among many client machines (VBA solution). For the
time tabling, I use batch updates. To date, these many thousands of updates
have not resulted in any problems or errors. The VBA solution and the SPROC
solution take about the same time to do the same thing. BTW, do you know
that one can largely duplicate one''s VBA code in SPROCS because one has
IFS, CASE and LOOPS available, variables, and UDFs there?
I could not advise anyone else about whether or not to use MDBs, or ADPs.
I''ve never used ODBC. I am by nature a problem solver, and quite compulsive
about code. I prefer a platform that does less for me, rather than one that
does more. I develop in ADPs and not in MDBs, and probably would not take
on an MDB job, even if it were quite lucrative. I think that ADPs are very
much advanced over MDBs in both concept and realization.
I write this to point out that at least one developer, (me), is both
committed to, and successful with ADPs, and has found no unsolvable
problems in working with them. He has sold ADP applications, and it seems
his clients are happy.
I have been working with databases since the time of DBaseIII, about 1983
(I think). I have progressed through FoxBase, FoxPro, Clipper and ...
Access. Clipper is likely to remain for me the most useful p-coding
language with which I have ever dealt, but I do like ADPs.
I am sorry if you feel that I should have attached this to one of the
current threads on this subject. I feel that I could not have done so
without contradicting what others have said, or confronting them. And I
simply wish to state my views, based on my experience. It is that ADPs are
great.
--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)
" Lyle Fairfield" <弥************ @ Invalid.Com>在消息中写道
新闻：Xn ******************* @ 130.133.1.4 ...
"Lyle Fairfield" <Mi************@Invalid.Com> wrote in message
news:Xn*******************@130.133.1.4...
我有现在已经开发了三年的ADP，包括Ac2K和AcXP。我已经为>
I have developed ADPs now for three years, in Ac2K and AcXP. I have sold
two ADP applications for >
这篇关于ADP ......另一种观点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
