转换访问MDB到ADP& MSDE 2000 [英] Conversion Access MDB to ADP & MSDE 2000
问题描述
大家好，
你好全部，
将MDB Access 2K2数据库转换为ToDo'/ Gotchas是什么？
前端的Access Project（即ADP）文件使用Microsoft
SQL Server 2000桌面引擎（MSDE 2000）作为后端？
现在为后台。我有一个原型MDB文件，内置在
Access 2K2中，并在Access 2K中编译，以提供与Access 2K的后向
兼容性。我有Office Professional 2K，& 2K2。我注意到
注意到Office Pro 2K2上提供了MSDE 2K，所以我认为我会尝试转换为
。
原型MDB文件使用DAO，记录集和&定制功能
广泛。 MDB文件的目的是生成最多4个数据桶/度量标准的YTD
或MTD报告。对于每个
桶/指标，您可以选择全部或特定的
详细信息之一。您可以在表单上为
报表选择期间和4个存储桶，然后从表单中运行报表。该表格对于
原型功能至关重要，有两种基本方式。首先，表单为基础报表的查询提供了
标准。其次，根据选择的
存储桶/指标确定报告的基础查询是如何定义的b
。每次重新定义查询是因为使用了使用Dsum作为分母生成的
百分比
用于百分比计算，总是看着相同的
命名查询。使用数学和4个桶/度量标准，可以从表单运行16个
不同的查询，具体取决于用户对桶/度量的选择。也许有另一种方式，但
它的工作原理。
由于我之前在Access中没有使用过单独的后端数据库，我
认为这将是一次很好的学习经历。我担心的是，由于使用了单独的后端数据库，因此MDB文件中使用的某些功能将无法实现
。是否必须在后端数据库中定义
报告的查询，或者我的
选项是什么？由于MDB文件对数据范围进行分类，因此我可以使用DAO和记录集来更新表中的数据。我可以在查询中使用
自定义函数吗？我怀疑我可能不得不以不同的方式做事情，并感谢你的指导/帮助。
TIA！
-
问候，
Greg Strong
Hello All,
Hello All,
What are the ToDo''s / Gotchas to convert an MDB Access 2K2 database to
an Access Project (i.e. ADP) file for the front end using Microsoft
SQL Server 2000 Desktop Engine (MSDE 2000) for the back end?
Now for the background. I have a prototype MDB file that was built in
Access 2K2, and compiled in Access 2K to provide backward
compatibility to Access 2K. I have Office Professional 2K, & 2K2. I
noticed MSDE 2K is provided on Office Pro 2K2, so I thought that I''d
try the conversion.
The prototype MDB file uses DAO, recordsets, & custom functions
extensively. The purpose of the MDB file is to generate either a YTD
or MTD report on up to 4 buckets/metrics of the data. For each
bucket/metric you can either select ''All'' or one of the specific
details. You choose the period and the 4 buckets on a form for the
report, then run the report from the form. The form is critical to the
prototype function in 2 basic ways. First, the form provides the
criteria for the underlying report''s query. Second, based upon the
buckets/metrics chosen determines how the report''s underlying query is
defined. The query is redefined each time due to the use of
percentages that are generated with the use of Dsum as the denominator
for the percentage calculation which is always looking at the same
named query. With the math and 4 buckets/metrics there are 16
different queries that can be run from the form depending upon the
user''s choice of the buckets/metrics. Maybe there is another way, but
it works.
Since I haven''t used a separate back end database before in Access, I
thought this would be a good learning experience. My concerns are that
some of the functionality used in the MDB file will not be possible
due to the use of a separate back end database. Do the queries for the
report have to be defined on the back end database, or what are my
options? Since the MDB file categorizes ranges of data will I be able
to use DAO and recordsets to update data in the tables. Can I use
custom functions in queries? I suspect I may have to do things
differently, and would appreciate your direction/help.
TIA!
--
Regards,
Greg Strong
推荐答案
开星期一，2005年10月31日17:51:40 GMT，Greg Strong< NoJunk@NoJunk4U2.com>
写道：
我看到一些红旗。最重要的一个我通过了MSDE ...所以我
以为我会尝试......。这不是一个很好的理由。在您的业余时间尝试
，并为您的客户/雇主提供
专业知识。特别是因为转换是非平凡的。从
您的问题我推断您对这个新的
环境知之甚少。 DAO可用，但不推荐。 ADP非常以ADO为中心。自定义VBA功能不可用。
在开始这个项目之前，学习ADP和SQL Server可能会更好。
。经常推荐的Access Developer
手册有一个关于ADP的第2部分。一个好的起点。
-Tom。
On Mon, 31 Oct 2005 17:51:40 GMT, Greg Strong <NoJunk@NoJunk4U2.com>
wrote:
I see a few red flags. The most important one "I notived MSDE ... so I
thought that I''d try...". That is NOT a good reason to do it. Try in
your spare time, and give your client/employer the benefit of your
expertise. Especially since the conversion is non-trivial. And from
your questions I infer you know very little about this new
environment. DAO is available, but NOT recommended. ADP is very much
ADO-centric. Custom VBA functions are NOT available.
It may be better to study ADP and SQL Server a bit more before
embarking on this project. The often-recommended "Access Developer
Handbook" has a Part 2 with a section on ADP. A good place to start.
-Tom.
大家好，
你好全部，
使用Microsoft将SQLB Access 2K2数据库转换为前端的Access项目（即ADP）文件的ToDo'/ Gotchas是什么？ 2000桌面引擎（MSDE 2000）用于后端？
现在为后台。我有一个原型MDB文件，内置在Access 2K2中，并在Access 2K中编译，以提供与Access 2K的后向兼容性。我有Office Professional 2K，& 2K2。我注意到Office Pro 2K2上提供了MSDE 2K，所以我认为我会尝试转换。
原型MDB文件使用DAO，记录集和&定制功能
广泛。 MDB文件的目的是生成最多4个桶/数据度量的YTD
或MTD报告。对于每个桶/度量标准，您可以选择全部或其中一个特定的详细信息。您可以在表单上为
报表选择期间和4个存储桶，然后从表单中运行报表。该表格以两种基本方式对原型功能至关重要。首先，表单提供了基础报表查询的
标准。其次，根据选择的桶/度量标准确定如何定义报告的基础查询。每次重新定义查询是由于使用了使用Dsum作为分母来生成的百分比，而百分比计算总是在查看相同的命名查询。使用数学和4个桶/指标，可以从表单中运行16个不同的查询，具体取决于用户对存储桶/指标的选择。也许还有另外一种方法，但
它的工作原理。
由于我在Access之前没有使用过单独的后端数据库，我认为这将是一个很好的学习经验。我担心的是，由于使用了单独的后端数据库，因此MDB文件中使用的某些功能将无法实现。是否必须在后端数据库上定义
报告的查询，或者我的
选项是什么？由于MDB文件对数据范围进行分类，因此我可以使用DAO和记录集来更新表中的数据。我可以在查询中使用
自定义函数吗？我怀疑我可能要做的事情不同，并感谢你的指导/帮助。
TIA！
Hello All,
Hello All,
What are the ToDo''s / Gotchas to convert an MDB Access 2K2 database to
an Access Project (i.e. ADP) file for the front end using Microsoft
SQL Server 2000 Desktop Engine (MSDE 2000) for the back end?
Now for the background. I have a prototype MDB file that was built in
Access 2K2, and compiled in Access 2K to provide backward
compatibility to Access 2K. I have Office Professional 2K, & 2K2. I
noticed MSDE 2K is provided on Office Pro 2K2, so I thought that I''d
try the conversion.
The prototype MDB file uses DAO, recordsets, & custom functions
extensively. The purpose of the MDB file is to generate either a YTD
or MTD report on up to 4 buckets/metrics of the data. For each
bucket/metric you can either select ''All'' or one of the specific
details. You choose the period and the 4 buckets on a form for the
report, then run the report from the form. The form is critical to the
prototype function in 2 basic ways. First, the form provides the
criteria for the underlying report''s query. Second, based upon the
buckets/metrics chosen determines how the report''s underlying query is
defined. The query is redefined each time due to the use of
percentages that are generated with the use of Dsum as the denominator
for the percentage calculation which is always looking at the same
named query. With the math and 4 buckets/metrics there are 16
different queries that can be run from the form depending upon the
user''s choice of the buckets/metrics. Maybe there is another way, but
it works.
Since I haven''t used a separate back end database before in Access, I
thought this would be a good learning experience. My concerns are that
some of the functionality used in the MDB file will not be possible
due to the use of a separate back end database. Do the queries for the
report have to be defined on the back end database, or what are my
options? Since the MDB file categorizes ranges of data will I be able
to use DAO and recordsets to update data in the tables. Can I use
custom functions in queries? I suspect I may have to do things
differently, and would appreciate your direction/help.
TIA!
要做：
1.研究MS-SQL Server 6个月;
2.然后学习ADO 4个月;
3.然后研究ADP 2个月;
4.然后开始转换;不要担心找到陷阱;
他们会找到你。
TO DO:
1. Study MS-SQL Server for 6 months;
2. Then Study ADO for 4 months;
3. Then Study ADPs for 2 months;
4. Then start your conversion; don''t worry about finding the gotchas;
they will find you.
" lylefair" < LY *********** @ aim.com>在消息中写道
news：11 ********************** @ g14g2000cwa.googlegr oups.com ...
"lylefair" <ly***********@aim.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
要做：
1.研究MS-SQL Server 6个月;
2.然后研究ADO 4个月;
3.然后研究ADP 2个月;
4.然后开始转换;不要担心找到陷阱;
他们会找到你。
TO DO:
1. Study MS-SQL Server for 6 months;
2. Then Study ADO for 4 months;
3. Then Study ADPs for 2 months;
4. Then start your conversion; don''t worry about finding the gotchas;
they will find you.
我的建议：重新阅读Lyle在这里写的内容。然后看看你是否可以谷歌他的
关于ADP的评论要求最终用户可以访问SQL
服务器_Tables_，这种情况有时会导致DBA陷入中风。
对于使用SQL Server通过ODBC的MDB而言，我对ADP的体验（通常是有限的）表明没有特别的优势。 ODBC选项确实具有
的优势，因为您可以将它与任何符合ODBC的服务器数据库一起使用。 ADP仅限于SQL Server及其变体 - 如果我没有记错，那么传统的MDB也是如此。
Larry Linson
Microsoft Access MVP
My advice: re-read what Lyle wrote here. Then see if you can Google his
comments about ADPs requiring that the endusers have access to the SQL
Server _Tables_, a situation that sometimes sends DBAs into apoplectic fits.
My (admittedly limited) experience with ADPs indicated no particular
advantage over MDB''s using SQL Server via ODBC. The ODBC option does have an
advantage in that you can use it with ANY server database that is
ODBC-compliant. ADPs are limited to SQL Server and its variants -- and, if I
am not mistaken, the traditional MDB, as well.
Larry Linson
Microsoft Access MVP
这篇关于转换访问MDB到ADP& MSDE 2000的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
