访问v点网 [英] Access v dot net

查看:50
本文介绍了访问v点网的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

只是看着C Sharp,看看它是否值得我学习

新东西。有没有人在这里尝试过.NET语言,试图复制

a现有的Access应用程序?

我有兴趣听听有关这个的故事,特别是

如何处理没有子表格 - 你能获得第三方控制

来填补这个空白吗?

Just looking at C Sharp to see if it might be worth my while learning
something new. Has anyone here tried a .NET language and tried to replicate
a existing Access app?
I would be interested to hear how any stories about this and in particular
how one deals with not having subforms - can you get a third-party control
to fill that gap?

推荐答案

" Deano" <德*** @ mailinator.com>写在

news:44 ********************** @ ptn-nntp-reader01.plus.net:
"Deano" <de***@mailinator.com> wrote in
news:44**********************@ptn-nntp-reader01.plus.net:
只是看看C Sharp,看看是否值得我学习新的东西。有没有人在这里尝试过.NET语言,并尝试复制现有的Access应用程序?
我很想听听有关这个以及
特别是如何处理没有子表单的故事 - 你能得到一个
第三方控制来填补这个空白吗?
Just looking at C Sharp to see if it might be worth my while learning
something new. Has anyone here tried a .NET language and tried to
replicate a existing Access app?
I would be interested to hear how any stories about this and in
particular how one deals with not having subforms - can you get a
third-party control to fill that gap?




有什么差距?除了控件中包含的表单外,子表单都没有。将

链接到模仿子表单的自己的表单可以很容易地用代码完成。

如果可以使用.net创建一个图形界面,那么当然可以

创建另一个,与子表格类似。


-

Lyle Fairfield



What gap? Subforms are nothing except forms contained in a control. Linking
to one''s own form that mimics a subform can be done very easily with code.
If one can create one graphical interface using .net then certainly can
create another, analagous to the sub-form.

--
Lyle Fairfield


Lyle Fairfield写道:
Lyle Fairfield wrote:
" Deano" <德*** @ mailinator.com>在
新闻中写道:44 ********************** @ ptn-nntp-reader01.plus.net:
"Deano" <de***@mailinator.com> wrote in
news:44**********************@ptn-nntp-reader01.plus.net:
只是看着C Sharp看看是否值得我学习新东西。有没有人在这里尝试过.NET语言,并尝试复制现有的Access应用程序?
我很想听听有关这个以及
特别是如何处理没有子表单的故事 - 你能获得一个
第三方控制来填补这个空白吗?
Just looking at C Sharp to see if it might be worth my while learning
something new. Has anyone here tried a .NET language and tried to
replicate a existing Access app?
I would be interested to hear how any stories about this and in
particular how one deals with not having subforms - can you get a
third-party control to fill that gap?



有什么差距?除了控件中包含的表单之外,子表单都没有。
使用代码可以很容易地链接到模仿子表单的自己的表单。如果可以使用
.net创建一个图形界面,那么肯定可以创建另一个,与子表单类似。



What gap? Subforms are nothing except forms contained in a control.
Linking to one''s own form that mimics a subform can be done very
easily with code. If one can create one graphical interface using
.net then certainly can create another, analagous to the sub-form.




谢谢,值得深思。我可能会看到使用C#

Express可以获得什么。



Thanks, food for thought. I might see what I can get accomplished using C#
Express.


这取决于你在做什么,你要部署到多少人,

以及你有多少耐心。哦,是的,你正在做什么样的预算/时间表




我几年前拿起VB.Net,构建了几个网络应用程序,体面的小

会计应用程序,以及其他一些实用程序。我喜欢它,但它在Access或甚至是VB6和它的前辈上都有很大的学习曲线。我讨厌写这个,但是花了6个月的时间才能成熟 -

,特别是在开发第一个网络应用程序时。


我仍​​然会在VB6中编写很多应用程序来获得今天处理器的性能优势。它开始很快并且随之而来。并且...

如果我是一个C junky ......当然,我会用C ++来做。你知道,在VB.NET上使用C#.NET真的没有什么好处。 CLR对待他们

相当公平 - 这只是一个偏好问题。另外,如果你是用b $ b来编写专有代码并将其发送到市场......请确保你进入混淆
混淆(加密源代码,将其部署到客户GAC)。


如果您的用户使用内置过滤,排序,数据表视图和所有内容的

,我将继续使用Access这是因为在另一个开发中重新创建所有这些东西需要花费相当多的时间来消耗它们。

环境。


您可以使用各种网格控件来使用子表单替换。

期待花费
This depends on what you are doing, how many people you are deploying to,
and how much patience you have. Oh yeah, and what kind of budget/timeline
you are working in.

I picked up VB.Net a few years ago, built several web apps, decent small
accounting app, and some other utilities. I like it, but it has a big
learning curve over Access or even VB6 and it''s predecessors. I hate to
write this, but it took 6 months to become anywhere near proficient -
especially in developing the first web app.

There are still a lot of apps I would write in VB6 to get a performance
advantage with today''s processors. It starts fast and gets with it. And...
if I was a C junky... well of course I would do it in C++. You see, there
really isn''t much advantage to go C#.NET over VB.NET. The CLR treats them
pretty darn fairly - it''s simply a matter of preference. Also, if you are
writing proprietary code and sending it to market... make sure you get into
obfuscation (scrambles source code that get''s deployed to the client GAC).

I would stay with Access if your users would have a big advantage using the
built in filtering, sorting, datasheet views, and all of that because it''s
fairly time consuming to re-create all that stuff in another development
environment.

You can use a variety of grid controls to make use of subform replacement.
Expect to spend around


这篇关于访问v点网的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆