Re: The future of various DB connection technologies and related technoloies



After 5 years of looking, waiting, learning, my gut feel is that
Microsoft is as much at a loss as we are. They have an objective of
evolving the platform (Windows) and evolving Office. In their evolutions,
they are incessantly preoccupied with several topics - dominating the web
space, elbowing into respectability in big iron (Oracle, Unix servers),
getting significant revenue from enterprise workflow (intranet portals,
data exchange between systems, rights management).

Since 997, they have already iterated through several revisions of web
technology (incorporating data access, browser content rendering, client-
server programming models) because the rest of the world rejected their
offerings.

They see XML as an empowering idea - it's structured data, meta data, an
RPC language, a data exchange medium over heterogenoeus platforms, a
programming language, a rendering language - you name it, they can Babel
it.

They see .NET as the successor to COM programming - .NET insulates the
programmer from Windows and Windows API and as a framework, challenges
Java successfully.

Where does Access, Jet and DAO/ADO fit in all this future? I think they
wish this would just all go away. All are COM. All are pre-XML meaning
that they have to duplicate effort in building additional COM XML
libraries for these things when their .NET framework is already rich in
XML functionality.

VB.NET is a replacement for VB6. SQL Server 2005 is a replacement for SQL
Server 6.5. They don't have a direct replacement in their new system for
Access, VBA and Jet. Their Office architecure is heavily COM and heavily
old - do they re-invent it completely in .NET?

Now Windows 64 bit is on the horizon. And Vista not far behind. Do they
simply port Office, VBA, DAO, ADO? Or do they re-engineer everything in
..NET for 64 bit since that framework is easier to migrate across?

Looking at the hype that is Web 2.0, the crazies think you don't even
need a desktop bound Office. Every Office function, they imply, can be
done in AJAX as web apps.

I think each current MS Office product team knows/decides what they want
to achieve for the current yet-to-be-released product. I don't they have
much idea of longer term or if they have an idea, that they can force it
to happen once their product revision has been released.

My 20 cents (that's the original 2 cents factored with inflation).



Lyle Fairfield <lylefairfield@xxxxxxx> wrote in
news:Xns9706825109236lylefairfieldaimcom@xxxxxxxxxxxxxx:

> It's confusing. Many people here and elsewhere make many different
> predictions:
.



Relevant Pages

  • Re: Installing CF app on a desktop or server
    ... I'm testing it on a clean install of XP SP 2 with no Framework installed. ... There are several reasons for this - like the fact that the CF engine would try calling Windows CE functions that don't exist or that exists in different locations. ... meaning they will just run under the full framework. ... If you mean a CE device acting as a server then the CF has no code security in it at all, so there's nothing you have to do to make it work. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Cannot re-install or uninstall .NET 1.1 on Windows 2003
    ... The 1.1 framework is indeed part of Server 2003, ... Phil Wilson [MVP Windows Installer] ... > Framework to install and function correctly. ...
    (microsoft.public.dotnet.framework.setup)
  • smtpmail send error (Access Denied or Error loading type library/DLL)
    ... invokeAttr, Object target, Objectargs, BooleanbyrefModifiers, ... I have this error only on one server, ... windows 2003 server US, framework 1.1, office 2003 with outlook ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: When to use AndAlso vs And ?
    ... framework I _PROBABLY_ have installed on these 7 machines? ... GAME02 - WIndows XP SP2 ... SQL8 - Quad Windows NT Server SP6 ... I probably have 20 different IDE throughout these ...
    (microsoft.public.dotnet.languages.vb)
  • Windows 98 logon problems on 2000 server
    ... windows 98 clients to logon to the domain. ... a new server running Windows 2000 starting basically from scratch as the old ... have a problem but since the server replacement, ... Domain Password you supplied is not correct, or access to your logon server ...
    (microsoft.public.win2000.security)

Loading