dotnet windows forms vs. Access

D

David W. Fenton

can see it working and even working well

I can't. I just don't see the point of all the work. The problems it
solves are so easily resolved without using temp tables that I don't
see the point of all the work to maintain them.
 
T

Tony Toews [MVP]

PMK said:
.NET version of an Access Data Project? I don't get it. Tell me more.

Unfortunately Aaron Ke mpf's answer to every problem is ADPs.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
S

Sylvain Lafontaine

Well, I suppose that depends on the type of MS-Office application that you
are using. XP-Pro is multithread but many applications are not multithread
or are poorly implementing any kind of multithread; so you should see no or
little increase of performance. Of course, Windows never stop doing
something and practically all applications are doing things like I/O; so you
will always benefit at least some advantage of running an application on a
bigger machine but by how much? I don't know.

However, you can tell that the more people will have dual and quad cores,
the more the number of applications that will get tuned to use this kind of
power.
 
S

Sylvain Lafontaine

Yeah, even me can get emphatic about something, sometime. It's only that in
this case (ADP), I got tired to hear people coming here to say that even if
they know nothing about SQL-Server, ADP or .NET - from their own admission
and they are proud of it, too - they will now tell us everything we need to
know about these.

As to VB6, I agree with you that on many occasions, it will be faster than
..NET. The problem here is not the performance when you are doing old stuff
like 10 years ago; the problem is when you want to have new stuff. When was
the last time that you have used some kind of datagrid control with VB6 and
that you didn't have the taste of eating your own keyboard after a few days
of work?

Something as simple as having rows of different colors can put VB6 or Access
down to their knees and I won't speak here about stuff like having images or
adding an unbound control to a continuous form or even something very basic
like keeping the multi-rows selection active when the user click on a
button.

When you need to add some extensibility of any kind, VB6/Access are simply
not the way to go.
 
R

Robert Morley

Yeah, okay, for the type of issues you're talking about, I can see .NET
being more useful. Last time I tried it, though, it was unacceptably slow,
and until someone can prove to me that the speed is now more
acceptable--which I've heard for 2005--and that there's a decent upgrade
path from VB6 (or better yet Access)--which I've never heard from
anybody--it won't ever be on my list of things to upgrade to.



Rob
 
S

Sylvain Lafontaine

There is no doubt that in comparaison of VB6/VBA, you need a lot of firing
power inside your machine to tame .NET but this is precisely what we are in
the process of getting this year as the basic configuration for a new
machine.

As for a decent upgrading path from Access, this is probably something we
should see next year. The SSMA-Access is already written in .NET, so I
won't be surprised if in one year or two there is a new version to upgrade
not only the backend to SQL-Server but also the frontend to .NET (and of
course with the option of upgrading only the FE, without touching the BE).
 
R

Robert Morley

Ummm...have you ever used the VB6 to VB.NET "Upgrade" Wizard? IIRC, it
doesn't upgrade forms at all, and it does a less-than-stellar job at
upgrading VB6 code. I can't say I have confidence in MS to write something
that will upgrade my FE in a way that would be better than simply starting
from scratch. (For me personally, my BE is already SQL Server, so that's
not an issue, though obviously that's strictly for me and not everybody.)


Rob
 
S

Sylvain Lafontaine

I must admit that there is a difference between an upgrade path and a decent
upgrade path. If I were the happy owner of MS, I would have put a little
more money into this upgrading wizard but as I'm not, ...
 
D

DAVID

Sylvain said:
I must admit that there is a difference between an upgrade path and a decent
upgrade path. If I were the happy owner of MS, I would have put a little
more money into this upgrading wizard but as I'm not, ...
There is a decent upgrade path from C to C#. MS put
a lot of time and effort into making sure that a VS C
project could be ported to VS.Net without tears.


I think it's like Vatican watching, or China watching as was. You see
the effects of the decisions that are made by some hidden process, and
then you get to work back from there and speculate about cause, and
speculate about possible future actions.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top