如何从MS Access应用程序到vb.net？ [英] how to get from an MS Access app to vb.net?

问题描述

我有一个完成的Microsoft Access应用程序，我们使用

Access运行时分发。这很好（大多数情况下），但我出售的优点是

dot.NET和升级到vb.NET似乎是一个未来的好主意。我是

也热衷于尽快在vb.NET中开发新软件。

我将研究如何移植应用程序以及如何使用ado。 NET等，但是我不确定我需要考虑的所有事情因此问题;


1.报告。我会想念Access''报告生成器。是否有一个

推荐的第三方应用程序？开发人员在使用vb.NET时会做出什么其他安排？


2.部署/远程更新应用程序。我从经验中了解到，

应用程序与您实际需要做的事情之间存在着一个完全不同的理论。 dot.NET在这个领域有多好？

我很乐意开发一个可以更新的Windows窗体应用程序，而不需要发送CD等等。 />

3.从Access迁移时可能存在重大差异。我读到了

在dot.NET或windows窗体中没有任何子表单。这是正确的吗？

mainform / subform概念是否以某种方式存在？我有重要的形式，

依赖于此，我无法看到解决这个问题的方法。当从Access转移到dot.NET以及重新编码等时，有没有人知道任何其他问题？


4.用户数据。我的应用程序允许用户备份和恢复他们创建的
数据。这是一个相当简单的过程，一旦我熟悉

与ado.NET？


应用程序仅限于在用户的PC上工作，没有服务器元素是

涉及。


非常感谢任何评论，链接等（我做了相当多的

研究谷歌群组但与访问相关的帖子至少或者询问

以获取将代码转换为dot.NET的内容。


视为

马丁

Hi,

I have a finished Microsoft Access app that we are distributing using an
Access runtime. This works fine (mostly) but I''m sold on the advantages of
dot.NET and upgrading to vb.NET seems like a good idea for the future. I''m
also keen to develop new software in vb.NET as soon as possible.
I will work out how to port the app and how to use ado.NET etc, however I''m
not certain about all the things I need to consider hence the questions;

1. Reporting. I will miss Access'' report generator. Is there a
recommended third-party app for this? What other arrangements do developers
make when using vb.NET?

2. Deployment/Remote updating of the app. I know from experience that
there is a world of difference between the theory concerting the deployment
of apps and what you actually need to do. How good is dot.NET in this area?
I''d love to develop a windows forms app that could be updated without
sending out a CD etc.

3. Possibly critical differences when moving from Access. I read that
there aren''t any subforms in dot.NET or windows forms. Is this right? Does
the mainform/subform concept exist in some way? I have important forms that
depend on this and I can''t see a way around this. Does anyone know of any
other issues when moving from Access to dot.NET apart from recoding etc?

4. User data. My app allows the user to back up and restore the data they
have created. Is this fairly straightforward process once I become familiar
with ado.NET?

The app is confined to working on the user''s pc and no server elements are
involved.

Many thanks for any comments, links etc (I have done a fair amount of
research on Google Groups but Access-related posts are at a minimum or ask
for something that converts code to dot.NET).

regards
Martin

推荐答案

嗨Deano，


我认为没有这个

新闻组中有这么多活跃的Access开发者，具有当前的Access体验。


这意味着当你想要在我看来与Access相比时答案

你永远得不到完整答案。 （仅限那些在短时间内完成了步骤的人）


Access是整个开发区域的一个子集，这意味着它

在某些部分非常有效，当你使用真正的开发语言时，它们可能需要更多的工作。


另一方面可以使用dotNet，很多事情都可以通过Access来实现，这是不可能的。

当你不需要那些时，那是你的决定。

只是我的想法，


Cor

Hi Deano,

I think that there are not so much active Access developers in this
newsgroup with current Access experience.

This means that when you want answers comparing with Access in my opinion
you never get a complete answer. (Only from the ones who did make the step a
short time ago).

Access is a subset from the complete development area, this means that it is
in some parts very effective and it wills probably in those parts need more
work when you are using a real development language.

On the other hand can there with dotNet, many things be done which are
impossible with Access.
When you do not need those, yea that is your decision.
Just my thought,

Cor

嗨Deano，


我认为在这个

新闻组中没有那么多活跃的Access开发人员具有当前的Access体验。


这意味着当你想要在我看来与Access相比答案

你永远得不到完整答案。 （仅限那些在短时间内完成了步骤的人）


Access是整个开发区域的一个子集，这意味着它

在某些部分非常有效，当你使用真正的开发语言时，它们可能需要更多的工作。


另一方面可以使用dotNet，很多事情都可以通过Access来实现，这是不可能的。

当你不需要那些时，那是你的决定。

只是我的想法，


Cor

Hi Deano,

I think that there are not so much active Access developers in this
newsgroup with current Access experience.

This means that when you want answers comparing with Access in my opinion
you never get a complete answer. (Only from the ones who did make the step a
short time ago).

Access is a subset from the complete development area, this means that it is
in some parts very effective and it wills probably in those parts need more
work when you are using a real development language.

On the other hand can there with dotNet, many things be done which are
impossible with Access.
When you do not need those, yea that is your decision.
Just my thought,

Cor

嗨Deano，


我已经在做你想做的事了，所以请理解

我的评论，虽然来自Access专家，来自一个dotnet新手。

任何dotnet专家如果我出错了请帮帮忙！

Hi Deano,

I''m already in the process of doing what you intend, so please understand
that my comments, whilst from an Access "expert", are from a dotnet newbie.
Any dotnet experts please help out if I get anything wrong!

1.报告。我会想念Access''报告生成器。是否有推荐的第三方应用程序？使用vb.NET时，b $ b开发人员还做了哪些其他安排？


水晶报告，大概是，但我还没有在我的应用程序中报告

但所以我不能评论CR反对访问报告。

2.部署/远程更新应用程序。我从经验中知道，与应用程序的
部署协调的理论和你实际需要做的事情之间存在着天壤之别。这个
区域的dot.NET有多好？我很乐意开发一个Windows窗体应用程序，可以在不发送CD等的情况下进行更新。


尚未使用dotnet进行部署，但我不喜欢不管怎么说，无论是通过CD还是通过网络或

，你都可以看到你如何期望更新应用程序而无需发送SOMETHING？我有时会发现部署Access应用程序非常麻烦：dotnet肯定不会更糟！

3.从Access迁移时可能存在重大差异。我读到了
dot.NET或windows窗体中没有任何子表单。这是正确的吗？
mainform / subform概念是否以某种方式存在？我有重要的形式
依赖于此，我无法看到解决这个问题的方法。除了重新编码之外，有什么人知道从Access到dot.NET的任何其他问题吗？


是的，没有子表格。如果你真的想要这样做，你需要准备重新设计你的用户界面

。我相信有一些方法可以在Windows窗体中拼凑一些类似Access的功能，但是不能访问它。我正在使用

数据网格显示数据，在Access中我将使用连续子表单，
并转向完全基于向导的方法来编辑/输入数据

例如如果用户想要创建一个新记录，他们点击相关的

按钮，一系列表格引导他们完成数据输入，然后

结果记录出现在数据网格。我认为这是一个积极的

移动：根据我的经验，将数据直接输入到复杂的Access表单中

会让用户感到困惑。但是，如果你必须拥有子表格和

连续表格，请坚持使用Access：这是它的最大优势，并且

没有其他类似的东西，AFAIK。

4.用户数据。我的应用程序允许用户备份和恢复他们创建的数据
。一旦我成为熟悉ado.NET的
，这是一个相当简单的过程吗？


什么数据库引擎？ SQL Server？当我使用链接的

SQL Server表完成Access应用程序时，我创建了菜单选项，允许用户将数据库备份到磁盘文件，还可以创建每天自动执行此计划

（使用SQL Server代理）。这非常简单，并且更像是一个SQL Server问题而不是客户端技术

问题。我期望使用dotnet实现相同的方法。


HTH


Baz


" Deano" <德********* @ hotmail.com>在消息中写道

新闻：Ux ********************* @ wards.force9.net ...

我有一个完成的Microsoft Access应用程序，我们使用
Access运行时分发。这很好（大多数情况下），但我卖的是dot.NET的优点
，升级到vb.NET对未来似乎是一个好主意。
我也热衷于尽快在vb.NET中开发新软件。
我将研究如何移植应用程序以及如何使用ado.NET等，但是
我不确定我需要考虑的所有事情因此问题;

1.报告。我会想念Access''报告生成器。是否有推荐的第三方应用程序？
开发人员在使用vb.NET时做了哪些其他安排？

2.部署/远程更新应用程序。我从经验中知道，与应用程序的
部署协调的理论和你实际需要做的事情之间存在着天壤之别。这个
区域的dot.NET有多好？我很乐意开发一个可以在不发送CD等情况下更新的Windows窗体应用程序。

3.从Access移动时可能存在重大差异。我读到了
dot.NET或windows窗体中没有任何子表单。这是正确的吗？
mainform / subform概念是否以某种方式存在？我有重要的形式
依赖于此，我无法看到解决这个问题的方法。除了重新编码之外，有什么人知道从Access到dot.NET的其他问题吗？

4.用户数据。我的应用程序允许用户备份和恢复他们创建的数据
。一旦我熟悉ado.NET，这是一个相当简单的过程吗？

该应用程序仅限于在用户的电脑上工作，并且不涉及任何服务器元素。

非常感谢任何评论，链接等（我已经对Google网上论坛进行了大量的研究，但访问相关的帖子至少或者询问
将代码转换为dot.NET。

问候语
Martin

1. Reporting. I will miss Access'' report generator. Is there a
recommended third-party app for this? What other arrangements do developers make when using vb.NET?
Crystal Reports, presumably, but I haven''t got around to reports in my app
yet so I can''t comment on CR as against Access reports.
2. Deployment/Remote updating of the app. I know from experience that
there is a world of difference between the theory concerting the deployment of apps and what you actually need to do. How good is dot.NET in this area? I''d love to develop a windows forms app that could be updated without
sending out a CD etc.
Haven''t deployed with dotnet yet, but I don''t quite see how you expect to
update apps without sending SOMETHING out, whether by CD or via the web or
whatever? I''ve sometimes found deploying Access apps to be very
troublesome: dotnet surely cannot be worse!
3. Possibly critical differences when moving from Access. I read that
there aren''t any subforms in dot.NET or windows forms. Is this right? Does the mainform/subform concept exist in some way? I have important forms that depend on this and I can''t see a way around this. Does anyone know of any
other issues when moving from Access to dot.NET apart from recoding etc?
Yep, no subforms. You need to be prepared to redesign your user interface
if you really want to do this. I believe there are ways to cobble together
some Access-like features in Windows Forms, but Access it ain''t. I am using
data grids to display data where in Access I would use a continuous subform,
and am moving to a completely Wizard-based approach to editing/entering data
e.g. if user wants to create a new record, they click on the relevant
button, a series of forms guides them through the data entry, and the
resulting record then appears in the data grid. I see this as a positive
move: in my experience, entering data directly into complex Access forms
confuses the hell out of users. But, if you must have subforms and
continuous forms, stick with Access: those are it''s greatest strengths, and
there is nothing else like it, AFAIK.
4. User data. My app allows the user to back up and restore the data they have created. Is this fairly straightforward process once I become familiar with ado.NET?

What database engine? SQL Server? When I have done Access apps with linked
SQL Server tables, I have created menu options that allow the user to backup
the database to a disk file, and also to create a schedule to do this
automatically every day (using SQL Server Agent). This is quite
straightforward, and is more a SQL Server issue than a client technology
issue. I expect to implement the same approach using dotnet.

HTH

Baz

"Deano" <de*********@hotmail.com> wrote in message
news:Ux*********************@wards.force9.net... Hi,

I have a finished Microsoft Access app that we are distributing using an
Access runtime. This works fine (mostly) but I''m sold on the advantages of dot.NET and upgrading to vb.NET seems like a good idea for the future. I''m also keen to develop new software in vb.NET as soon as possible.
I will work out how to port the app and how to use ado.NET etc, however I''m not certain about all the things I need to consider hence the questions;

1. Reporting. I will miss Access'' report generator. Is there a
recommended third-party app for this? What other arrangements do developers make when using vb.NET?

2. Deployment/Remote updating of the app. I know from experience that
there is a world of difference between the theory concerting the deployment of apps and what you actually need to do. How good is dot.NET in this area? I''d love to develop a windows forms app that could be updated without
sending out a CD etc.

3. Possibly critical differences when moving from Access. I read that
there aren''t any subforms in dot.NET or windows forms. Is this right? Does the mainform/subform concept exist in some way? I have important forms that depend on this and I can''t see a way around this. Does anyone know of any
other issues when moving from Access to dot.NET apart from recoding etc?

4. User data. My app allows the user to back up and restore the data they have created. Is this fairly straightforward process once I become familiar with ado.NET?

The app is confined to working on the user''s pc and no server elements are
involved.

Many thanks for any comments, links etc (I have done a fair amount of
research on Google Groups but Access-related posts are at a minimum or ask
for something that converts code to dot.NET).

regards
Martin

这篇关于如何从MS Access应用程序到vb.net？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！