Noobie问题：将数据集挂钩到.MDB？ [英] Noobie Question: Hooking a dataset into .MDB?
问题描述
我即将开始攀登.Net学习曲线。
想从复制一个我已经拥有的小应用程序开始
并使用MS Access前端运行。它管理班级
团聚的信息。似乎有基本知识：父/子记录，查找
功能，添加/更改/删除功能....
但是我不喜欢我不想只开发一个客户端/服务器应用程序，而不是.Net。
相反，我想要整整九码并使用.Net DataSet。
我想尽量减少TB处理的新东西的数量。
考虑在JET后端实现DataSet是否现实？
（即不能写入任何存储过程）
或者我应该咬紧牙关将后端迁移到SQL Server？
-
PeteCresswell
I''m about to start climbing the .Net learning curve.
Would like to start by reproducing a little application that I already have up
and running using an MS Access front end. It manages information for class
reunions. Seems to have the basics: parent/child records, "Find"
functionality, Add/Change/Delete functionality....
However I don''t want to develop just a client/server app shoehorned into .Net.
Instead, I''d like to go the whole nine yards and use .Net DataSets.
I''d like to minimize the number of new things TB dealt with.
Is it realistic to think about implementing DataSets against a JET back end?
(i.e. no stored procedures can be written)
Or should I just bite the bullet an migrate the back end to SQL Server?
--
PeteCresswell
推荐答案
"（Pete Cresswell）" < x@y.z>在消息中写道
news：6p ******************************** @ 4ax.com ...
"(Pete Cresswell)" <x@y.z> wrote in message
news:6p********************************@4ax.com...
我即将开始攀登.Net学习曲线。
想从复制我已经拥有的一个小应用程序开始使用MS Access前端运行
。它管理
班级团聚的信息。似乎有基本知识：父/子记录，查找功能，添加/更改/删除功能....
但是我不想只开发一个客户端/服务器应用程序进入了
.Net。
相反，我想要整整九码并使用.Net DataSet。
我想要尽量减少结核病处理的新事物的数量。
考虑实施DataSet对抗JET结束是否现实？
（即不能编写存储过程）
<或者我应该咬紧牙关将后端迁移到SQL Server？
I''m about to start climbing the .Net learning curve.
Would like to start by reproducing a little application that I already
have up
and running using an MS Access front end. It manages information for
class
reunions. Seems to have the basics: parent/child records, "Find"
functionality, Add/Change/Delete functionality....
However I don''t want to develop just a client/server app shoehorned into
.Net.
Instead, I''d like to go the whole nine yards and use .Net DataSets.
I''d like to minimize the number of new things TB dealt with.
Is it realistic to think about implementing DataSets against a JET back
end?
(i.e. no stored procedures can be written)
Or should I just bite the bullet an migrate the back end to SQL Server?
您不需要使用存储过程来创建数据集。任何查询都可以使用适当的DataAdapter加载到数据集中，在这种情况下，
将是OleDbDataAdapter，我相信。
You don''t need to use stored procedures to create datasets. Any query can be
loaded into a dataset using the appropriate DataAdapter, in this case that
would be OleDbDataAdapter, I believe.
您可以通过OleDbClients使用JET后端。虽然我会建议反对它;）在我的opionon中，访问不是一个数据库（甚至不是一个实际的数据库，只是一个文件）值得大惊小怪。
不知道你的应用程序在做什么，但MSDE可能是一个便宜的
替代。
-
Patrik L？wendahl [C＃MVP]
www.cshrp.net - 诙谐的程序员优雅的代码
"（Pete Cresswell）" < x@y.z>在消息中写道
news：6p ******************************** @ 4ax.com ...
You could use a JET backend through the OleDbClients. Although I would
advise against it ;) Access isn''t, in my opionon, a "database"(Not even a
real db, just a file) worth the fuss.
Don''t really know what your app is doing, but the MSDE could be a cheap
substitue.
--
Patrik L?wendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"
"(Pete Cresswell)" <x@y.z> wrote in message
news:6p********************************@4ax.com...
我即将开始攀登.Net学习曲线。
想从复制我已经拥有的一个小应用程序开始使用MS Access前端运行
。它管理
班级团聚的信息。似乎有基本知识：父/子记录，查找功能，添加/更改/删除功能....
但是我不想只开发一个客户端/服务器应用程序进入了
.Net。
相反，我想要整整九码并使用.Net DataSet。
我想要尽量减少结核病处理的新事物的数量。
考虑实施DataSet对抗JET结束是否现实？
（即不能编写存储过程）
<或者我应该咬紧牙关将后端迁移到SQL Server？
-
PeteCresswell
I''m about to start climbing the .Net learning curve.
Would like to start by reproducing a little application that I already
have up
and running using an MS Access front end. It manages information for
class
reunions. Seems to have the basics: parent/child records, "Find"
functionality, Add/Change/Delete functionality....
However I don''t want to develop just a client/server app shoehorned into
.Net.
Instead, I''d like to go the whole nine yards and use .Net DataSets.
I''d like to minimize the number of new things TB dealt with.
Is it realistic to think about implementing DataSets against a JET back
end?
(i.e. no stored procedures can be written)
Or should I just bite the bullet an migrate the back end to SQL Server?
--
PeteCresswell
Patrik Lowendahl [C＃MVP]" < PA ************** @ csharpsweden.com>写在
消息新闻：ux ************** @ TK2MSFTNGP12.phx.gbl ...
"Patrik Lowendahl [C# MVP]" <pa**************@csharpsweden.com> wrote in
message news:ux**************@TK2MSFTNGP12.phx.gbl...
你可以使用JET后端通过OleDbClients。虽然我会建议反对它;）访问不是，在我的opionon中，一个数据库（甚至不是真正的数据库，只是一个文件）值得大惊小怪。
我真的不知道你的应用程序在做什么，但是MSDE可能是一个便宜的替代品。
You could use a JET backend through the OleDbClients. Although I would
advise against it ;) Access isn''t, in my opionon, a "database"(Not even a
real db, just a file) worth the fuss.
Don''t really know what your app is doing, but the MSDE could be a cheap
substitue.
MSDE会起作用，但是它有点沉重的锤子，你不觉得吗？
如果，在这种情况下，这只是一个单一的用户，小应用程序，Access是
可能是正确的选择，如果没有其他原因，因为它具有
最小的占地面积和安装过程。
MSDE would work, but its a bit of a heavy hammer, don''t you think?
If, in this case, this is simply a single user, small application, Access is
probably the right choice, if for no other reason than because it has the
smallest footprint and installation process.
这篇关于Noobie问题：将数据集挂钩到.MDB？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
