Re: Is ADO dead?

David W. Fenton wrote:
CDMAPoster@xxxxxxxxxxxxxxxx wrote in
news:1140467379.516010.154970@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

Darryl Kerkeslager wrote:
"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote

Well, not dead, but renamed, which suggests that any
documentation using the term "MSDE" is out of date, and,
perhaps obsolete.

No - it is dead - in the same sense that people have referred to
ADO and DAO as dead - it is no longer being developed. In fact,
MSDE is more dead than DAO, in that there is no longer any
logical reason to use it, as SQL Server Express more than takes
the place of it.

SQL Server Express is not MSDE, any more than ADO.Net is ADO, or
MSDE is SQL Server.


--
Darryl Kerkeslager

This is interesting. In spite of it being called Access 12,
Microsoft is really eliminating Access and VBA. SQL Server
Express for the data and .NET for the interface with definitions
and reporting in XML.

Huh? Where in the world are you getting this information? Surely not
from the Access 12 blog on MSDN, which has said nothing of the sort.


It's possible that ADO and DAO will be available in Access 12 but SQL
Server Express without VBA definitely seems to be where MS is heading.
I have not seen any indication anywhere that VBA will be able to be
used in Access 12 at all. I may be wrong. If you need to customize
the output before or after it's created you need something like Visual
Studio or FrontPage or something else. XML is not just used as a
storage mechanism. If Access 12 can't create the XML you need, then
VBA is not an option.

[cliche alert] It's starting to look like they dumped the RAD baby
out with the bathwater. . . .

If your major premise is wrong, your minor premise cannot be proven.

That may be so, but VB.NET or C# is quite a bit slower to develop in
than VBA.

. . . That is, unless you falsely imagine that the extra
flexibility MS designed into Access 12 reporting will be able to
handle every situation. . ..

They are keeping the same report designer UI and adding a new Layout
view, which is like an editable print preview. Sounds like a good
thing to me -- use the old methods where they work best, and the new
ones where those are better.

No VBA behind a report. So much for the old methods. If you're happy
with what Access 12 can do natively then things are better with the new
design.


How the report definition is actually stored is really completely
irrelevant to me, as I don't have access to that, in any case,
unless I want to do a SaveAsText (which I never do, unless I'm
trying to recover a corrupted report).

The XML for the report is already in plain text. SaveAsText won't help
corrupted reports. You'll need to start indenting the XML source for
that :-).


. . . MS had good reasons for going in these directions so
I'll try not to mourn the death of Access too long. . . .

What in the world are you talking about?

Everything needed to move toward something that would work for the
internet/intranet world. I was talking about eliminating VBA and the
way mdb files are stored. Those are good things in the long run. I
just need to find something that makes up for the loss of VBA.


. . . I'll do the best I
can to create a RAD environment without what we once understood
Access to be. [cliche alert] Putting Access' clothes on .NET
reminds me of a certain silk pigskin wallet. [cliche alert] It
seems that the reports of Access' demise were not premature.

Are you completely insane? None of the things you are talking about
are going to happen according to the official Access blog on MSDN.

None.

I don't think it's going to be Access anymore. I think it's going to
be SQL Server and .NET with some flexible XML writing thrown in. I
think it's going to be more powerful than before. I think the
development process will be slower. Visual C++ is extremely powerful
but I don't design databases with it. I hope you're correct about
being able to use ADO or DAO like before without resorting to .NET
coding. I don't think that the new flexibility that reports are going
to have is enough to justify calling the new .NET thing Access. Even
custom SQL will have to be part of the .NET code. [mangled cliche
alert] If it looks, sounds and acts like .NET then it is a dog :-).

James A. Fortune
CDMAPoster@xxxxxxxxxxxxxxxx

.

Relevant Pages

  • Re: Is ADO dead?
    ... No - it is dead - in the same sense that people have referred to ... MSDE is more dead than DAO, in that there is no longer any ... as SQL Server Express more than takes ... They are keeping the same report designer UI and adding a new Layout ...
    (comp.databases.ms-access)
  • Re: Is ADO dead?
    ... as SQL Server Express more than takes ... Microsoft is really eliminating Access and VBA. ... and reporting in XML. ... They are keeping the same report designer UI and adding a new Layout ...
    (comp.databases.ms-access)
  • Re: Difference between MSDE 7 and SQL 7
    ... Alan is right, but there are also .NET Framework factory classes that can ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server 2005 Express Edition is the MSDE replacement for SQL Server ... statement it will report the version of SQL Server 7.0 (MSDE or an edition ...
    (microsoft.public.sqlserver.msde)
  • Re: Is ADO dead?
    ... Microsoft is really eliminating Access and VBA. ... definitions and reporting in XML. ... Server Express without VBA definitely seems to be where MS is ... No VBA behind a report. ...
    (comp.databases.ms-access)
  • Re: MS Access Reports and VB.NET Program
    ... think that I want to ship a 30mb .NET framework to each of my clients? ... Barns & Noble has some books that could help you learn .NET. ... It is Access TIMES eCommerce TIMES Sql Server. ... that you actually posted how to execute the report using a macro. ...
    (microsoft.public.dotnet.languages.vb)