clintonG said:
Microsoft is not advocating the use of the outdated JET database you
refer to as Access.
You are mistaken in three ways. First, after a period of SQL Server
evangleism, Microsoft has stepped back from recommending "SQL Server
everywhere", and is now recommending Jet databases for appropriate uses.
Second, Access is not Jet, but a user-interface and
application-development program that happens to use Jet as its default
file-server database. Access works just as well with a SQL Server
back-end. And third, this is not a question about data-storage
mechanisms; it's a programming question for which any debate about what
the superiority of one back-end database or another is entirely
irrelevant. John's original question was posted to two Access
newsgroups, from which I think it's reasonable to conclude that he
already has an Access application to which he wants to add this
functionality.
I contend if this project were to be implemented
using JET and given the credibility of the business case for doing
so, everything we know about the JET database indicates it would need
to be replaced shortly after deployment.
I wonder what it is you think you know about Jet. But again, the
question is really about programming, not about databases as such..
It would be okay to use as a
prototype given other business considerations for doing so but I
don't think the OP (John) asked how to develop a prototype and as I
understand it Microsoft is no longer releasing any new versions of
JET.
Jet is currently in maintenance mode, but since various OS components
rely on it, I don't think it's going away any time either. MS currently
doesn't have any other database product that fills the same niche. When
they develop one, I expect Access will work with it.
I agree with Microsoft who now advocates the use of SQL Server 2005
Express (SQLX) as it provides native support for XML and provides
many other benefits.
TTBOMK, Microsoft is not, as a corporation, currently advocating SQLX as
a replacement for Jet. The SQL Server design team may be.
Furthermore, John is on a fact finding mission. If he follows my
leads he will become informed of the 'big picture.' For example, I
already understand that he wants to deploy Smart Clients but he
doesn't even know what that means yet. Furthemore, he will soon learn
he needs a good plan to get to where he wants to go.
Your view of what John is after and what he needs, like mine, is based
on very little information. But I think you're mistaken.
I mean, the suggestion to use JET as stated at best provides a base
level of backwards compatibility. I think it is important to
challenge each prospective client as it is them and them alone who
must determine if they want to work with a backwards solution when I
offer to help them learn to go forward.
I agree with your philosophical statement, but I think you know very
little about Access.