访问vs Visual Studio dot.net [英] Access vs Visual Studio dot.net

问题描述

大家好。

我是Access开发人员，曾与Access-dev合作过。在Sql server数据库和Access上花了很多年的时间。

对于互联网我一直在使用传统的asp。

但是现在我试过了asp.net和这个工具对我来说很棒。


Haven没有尝试过Vb for Visual Studio net，但希望能够在非常好的情况下实现这个目标。\\ b
未来。

希望这个版本的vb与asp.net很好用，虽然我不知道如何。


但是我正在考虑让Access继续使用

Visual studio dot.net进行新项目。


所以大家：你认为我我正在做正确的事情移动到Visual

studio dot.net？

Hi everyone.
I am an Access developer having worked with Access-dev. projects for
many years on Sql server databases and Access.
For the internet I have been using traditional asp.
But now I have tried asp.net and this tool seemes great to me.

Haven''t tried Vb for Visual Studio net, but hope to do that in the very
future.
Hope that this version of vb goes well together with asp.net although I
don''t know how.

However I am therefore thinking about leaving Access for working with
Visual studio dot.net for new projects.

So folks: Do you think that I am doing the right thing moving to Visual
studio dot.net?

推荐答案

2005年2月3日23:57:02 -0800， ol**@ylm.se 写道：

On 3 Feb 2005 23:57:02 -0800, ol**@ylm.se wrote:

你好大家。
我是Access开发人员，曾与Access-dev合作过。在Sql server数据库和Access上多年的项目。
对于互联网，我一直在使用传统的asp。
但是现在我尝试了asp.net，这个工具对我来说很棒。<但是，Haven没有尝试过Vb for Visual Studio net，但希望在未来很好的时候做到这一点。
希望这个版本的vb与asp.net很好地结合在一起我不知道怎么做。

然而我正考虑让Access与
Visual studio dot.net合作开展新项目。
studio dot.net吗？

Hi everyone.
I am an Access developer having worked with Access-dev. projects for
many years on Sql server databases and Access.
For the internet I have been using traditional asp.
But now I have tried asp.net and this tool seemes great to me.

Haven''t tried Vb for Visual Studio net, but hope to do that in the very
future.
Hope that this version of vb goes well together with asp.net although I
don''t know how.

However I am therefore thinking about leaving Access for working with
Visual studio dot.net for new projects.

So folks: Do you think that I am doing the right thing moving to Visual
studio dot.net?

我不想如果它是正确的话或不。对于许多工作来说，访问仍然是最好的工具，但如果这些工作不是你正在做的工作，那么.NET或

Java平台可以提供更好的语言和开发工具。

I wouldn''t want to say if it was "right" or not. Access is still the best
tool for many jobs, but if those aren''t the jobs you are doing, the .NET or
Java platforms provide better languages and development tools.

ol**@ylm.se 写道：

ol**@ylm.se wrote:

所以大家好：你认为我正在做正确的事情转移到Visual
studio dot.net吗？

So folks: Do you think that I am doing the right thing moving to Visual
studio dot.net?

我认为你做了正确的事情远离Access。


可能没有那么多好地方可以移动。


长对于开发商而言，MS可能并不是很好，因为MS购买了FoxPro，CA购买了Clipper。谁知道我们可能会有什么奇迹

现在让这些产品自己移动到GUI？


我可能会再看看FoxPro，12我放弃它多年后。我是看着各种J的
。事情。


我开始认为所有关于客户端服务器dbs的喧嚣如

MS-SQL可能只是那个，喧嚣和对于许多开发人员而言，使用

文件dbs，使用本土安全性可能允许优越的开发。

将数据，索引，程序组合在同一文件中的逻辑已经

失去了我的有效性。为什么？咦？为了保护我们自己？


我对MS非常失望。


-

-

Lyle

-

来自ADO28.chm


不推荐使用的组件

以下每个组件都被视为已过时。虽然这个版本的微软仍然支持这些

组件？数据

访问组件（MDAC），将来可能会将其删除。当

编写新的应用程序时，你应该避免使用这些已弃用的

组件。修改现有应用程序时，强烈建议您删除对这些组件的依赖。


ODBC提供程序（MSDASQL）

强烈建议您使用其中一个本机OLE DB提供程序

而不是Microsoft开放式数据库连接（ODBC）提供程序。

本机OLE DB提供程序提供更好的应用程序稳定性和

表现。此外，未来将在

中支持本机OLE DB提供程序，而MSDASQL将不会添加任何新功能，

将无法在64位上使用， OLE将无法访问OLE

DB NET数据提供程序。


远程数据服务（RDS）
远程数据服务（RDS）是一种专有的Microsoft机制，用于通过Internet或Intranet访问远程数据。
。微软现在提供微软简单对象访问协议（SOAP）工具包2.0

，使您能够使用基于XML的开放式访问远程数据

标准。鉴于SOAP Toolkit 2.0的可用性，您应该将
从RDS迁移到SOAP。 SOAP 2.0 Toolkit 2.0还包括用于远程访问Microsoft ActiveX的示例

代码？数据对象（ADO）

记录集。


Jet和复制对象（JRO）

Microsoft Jet OLE DB提供程序和其他从MDAC 2.6中删除相关组件

。 Microsoft已弃用Microsoft Jet

引擎，并且不计划为此组件提供新版本或服务包。

因此，Jet和复制对象（JRO）正在在此版本中已弃用

，将来不会在任何MDAC版本中提供。


.....

I think you have done the right thing moving away from Access.

There may not be so many great places to move.

In the long run it may not have been wonderful for the developer that MS
bought FoxPro, that CA bought Clipper. Who knows what marvels we might
have now had these products made the move to a GUI by themselves?

I may take a another look at FoxPro, 12 years after I abandoned it. I''m
looking at various "J" things.

I''m beginning to think that all the hoopla about client-server dbs like
MS-SQL may be just that, hoopla, and that for many developers the use of
file dbs, with home-grown security may be allow superior development.
The logic of combining data, indexes, procedures in the same file has
lost its validity with me. Why? Huh? To protect us from ourselves?

I am very disillusioned with MS.

--
--
Lyle
--
From ADO28.chm

Deprecated Components
Each of the following components is considered obsolete. While these
components are still supported in this release of the Microsoft? Data
Access Components (MDAC), they may be removed in the future. When
writing new applications, you should avoid using these deprecated
components. When modifying existing applications, you are strongly
encouraged to remove any dependency on these components.

ODBC Provider (MSDASQL)
You are strongly encouraged to use one of the native OLE DB Providers
instead of the Microsoft Open Database Connectivity (ODBC) Provider.
Native OLE DB Providers provide better application stability and
performance. Furthermore, native OLE DB Providers will be supported in
the future, whereas MSDASQL will not have any new features added to it,
will not be available on 64-bit, and will not be accessible from the OLE
DB NET Data Provider.

Remote Data Services (RDS)
Remote Data Services (RDS) is a proprietary Microsoft mechanism for
accessing remote data across the Internet or intranet. Microsoft is now
shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit 2.0
that enables you to access remote data using an open, XML-based
standard. Given the availability of the SOAP Toolkit 2.0, you should
migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes sample
code for remotely accessing Microsoft ActiveX? Data Objects (ADO)
Recordsets.

Jet and Replication Objects (JRO)
The Microsoft Jet OLE DB Provider and other related components were
removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
Engine, and plans no new releases or service packs for this component.
As a result, the Jet and Replication Objects (JRO) is being deprecated
in this release and will not be available in any future MDAC releases.

.....

过去几年我一直在为

做MS Access和ASP.NET（使用VB.NET）。我没有使用.NET平台来创建Windows

表单。客户端/服务器应用程序，但我看了它。我会说

以下内容：


*从VB到VB.NET从语法上来说对你没问题

的观点。但是，您需要在.NET平台中学习非常庞大的对象库（或名称空间）。为了从.NET平台中获得最多的好处，你可能还需要了解一些面向对象编程概念的b $ b。一本好书将非常有价值。


*如果您为.NET开发一个Windows窗体应用程序，您的客户端机器将是

都需要安装.NET框架。对于拥有所有新设备的客户来说，这不是什么大不了的事。

但是它可能出现在许多其他

的情况下。请注意，对于ASP.NET Web应用程序来说，这不是问题，只有服务器需要.NET框架才能使用
。


*请记住访问 ;是一个数据库（Jet）和一个工具，用于创建一个全部包含在一个用户界面的
。在.NET中进行开发时，您仍然需要一个

数据库，就像使用VB6时一样。 MS

Access（Jet）可能是您在某些情况下使用的数据库

所以不要放弃MS Access。


*使用Visual Studio.NET 2002/3，您必须在每次更改代码时重新编译项目。这使得调试比在MS-Access中调试慢很多，你可以实际更改代码

。我相信你可以使用适用于Windows窗体应用程序的新VS 2005（Whidbey）执行此操作。

不幸的是，我们的ASP.NET开发人员仍然需要据我所知，重新编译（或者

至少等待自动编译）。


*你会喜欢使用SQL Server中包含的工具

Visual studio.NET。您甚至可以单步调试存储的

过程和用户​​定义的函数。我几乎完全使用VS.NET来进行数据库设计，我敢打赌你也会尝试它。


*对于简单的应用程序，使用.NET将是过度的。在MS Access中，

你有一些简单的控件可以根据需要自定义 - 几乎没有选择
并且不会混淆使用什么。在VB6中，你有一些库

的控件可供选择和编织到一个应用程序中。你

也可以使用第三方控件。从我看到的.NET windows

应用程序来看，选择更大（更好）。你的开发时间

毫无疑问会增加。


因此，我会说你绝对应该毫无疑问

学习.NET平台并学习用.NET创建应用程序。

但是，不要放弃MS Access。将两个工具放在你的工具带中并且每个人都适当地使用它们。


Bill E.

好​​莱坞，佛罗里达州> ol**@ylm.se 写道：

I have been doing both MS Access and ASP.NET (using VB.NET) for the
past few years. I have not used the .NET platform to create a "Windows
forms" client/server application but I have looked at it. I would say
the following:

*Going from to VB to VB.NET will be no problem for you from a syntax
point of view. You will, however, need to learn the incredibly vast
object libraries (or "namespaces") in the .NET platform. To benefit
the most from the .NET platform, you may also want to brush up on some
of your object-oriented programming concepts. A good book will be
extremely valuable.

*If you develop a windows forms app for .NET, your client machines will
all need to have the .NET framework installed. This isn''t a big deal
for a customer with all new equipment but it may be in many other
situations. Note that this isn''t a problem for ASP.NET web apps where
only the server needs the .NET framework.

*Remember that "Access" is both a database (Jet) and a tool for
creating a user interface all wrapped up in one. You will still need a
database when developing in .NET just as you did when using VB6. MS
Access (Jet) could be the database that you use in certain situations
so don''t abandon MS Access.

*With Visual Studio.NET 2002/3 you had to recompile your project every
time you made a change to your code. This makes debugging a lot slower
than it would be in MS-Access where you can actually change the code
while you''re stepping through it. I believe that you will be able to
do this with the new VS 2005 (Whidbey) for windows forms apps.
Unfortunately, we ASP.NET developers will still need to recompile (or
at least wait for the automatic compilation) as far as I know.

*You will love the tools for working with SQL Server contained in
Visual studio.NET. You can even step through and debug your stored
procedures and user-defined functions. I use VS.NET almost exclusively
to do database design and I''ll bet that you will too after trying it.

*For simple applications, using .NET will be overkill. In MS Access,
you have a few simple controls that you can customize as needed--few
choices and no confusion about what to use. In VB6, you have libraries
of controls from which to choose and weave into an application. You
can also use third party controls. From what I see from .NET windows
apps, the choices are even larger (and better). Your development time
will increase without a doubt.

Therefore, I would say that you should absolutely without question
learn the .NET platform and learn to create applications in .NET.
However, don''t abandon MS Access. Keep both tools in your toolbelt and
use each of them appropriately.

Bill E.
Hollywood, FL
ol**@ylm.se wrote:

大家好。
我是一名Access开发人员与Access-dev合作过。在Sql server数据库和Access上多年的项目。
对于互联网，我一直在使用传统的asp。
但是现在我尝试了asp.net，这个工具对我来说很棒。<没有尝试过Vb for Visual Studio net，但希望在未来的
中做到这一点。
希望这个版本的vb与asp.net很好地结合在一起
我不知道怎么做。

然而我正在考虑让Access为Visual Studio dot.net工作
用于新项目。
Visual studio dot.net吗？

Hi everyone.
I am an Access developer having worked with Access-dev. projects for
many years on Sql server databases and Access.
For the internet I have been using traditional asp.
But now I have tried asp.net and this tool seemes great to me.

Haven''t tried Vb for Visual Studio net, but hope to do that in the very future.
Hope that this version of vb goes well together with asp.net although I don''t know how.

However I am therefore thinking about leaving Access for working with Visual studio dot.net for new projects.

So folks: Do you think that I am doing the right thing moving to Visual studio dot.net?

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