Re: ADP or MDB - which is a better front end for SQL Server?
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Mon, 9 May 2005 12:37:57 -0400
As you said, the real question here is the possible (future) integration of
the CLR into the JET/MDB couple. Obviously, MS won't call you at home to
remove your MDB files on your home computer but if the JET/MDB remains
inchanged, I don't see what future it could have when the next version of
Windows, Longhorn, will came out on the market.
Sometime - even when you don't want it or like it - you need to have your
program communicates with the exterior and this is especially true for
enterprise application, even when you don't need to interface with
SQL-Server. For example, when I've integrated the payment by credit card on
the Renaud-Bray web site, I didn't have any choice on the tools for doing
it. Now that VB6 is gone; the only thing that remains for making COM/COM+
components if VC++. It would be a very strange situation indeed to see MS
promoting the use of the MDB format on Longhorn without giving these
applications an easy access of communicating with the local operating system
environment. For those who are already the happy owners of a current
version of Windows, either Win95, 98, 2000 or XP; the MDB format will be
kept running for a long time (well, until the hard drive on these machines
crash). But when Longhorn will be released to the market next year; the
only logical choice that I see MS could take would be simply to drop the MDB
format without any further question in any new version of Access/Office.
But I may be wrong and it is well possible that we will see in the futur a
full integration of the CLR and of the .NET Framework - including the
ADO.NET objects - into JET and MDB.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
"Alex White MCDBA MCSE" <alex@xxxxxxxxxxxxxx> wrote in message
news:e91RhuKVFHA.1604@xxxxxxxxxxxxxxxxxxxxxxx
> You should be doing your recipes in XML, access if far to heavy weight, no
> really access is still has the largest user base out of all the smaller
> relational databases, MS cannot get rid of it for a while yet, but I have
> the feeling that it is going to end up managed (.net) but who knows.
>
> --
> Regards
>
> Alex White MCDBA MCSE
> http://www.intralan.co.uk
>
> "Jesper F" <jf> wrote in message
> news:427f7430$0$635$ba624c82@xxxxxxxxxxxxxxxxxxxxxx
>>> For MDB, they will be kept around a little more longer but only for
>>> supporting these innumerable kitchen recipes' databases that already
>> exists.
>>
>> I wonder what they intend to do with all those recipe databases out there
>> then?
>> Even though MS may be trying to introduce new technology the need for
>> small
>> databases and apps that are easy to develop won't dissappear.
>> I don't know much about .net but a quite a bit about Access and it serves
>> a
>> huge need with it's easy development and deployment. If it disappear's it
>> seems to me there'll be something missing in the bottom segment of
>> database
>> technology.
>> It'll be interesting to see what happens.
>>
>> Jesper Fjølner, Denmark
>>
>>
>>
>
>
.
- Follow-Ups:
- Re: ADP or MDB - which is a better front end for SQL Server?
- From: Paul Ponzelli
- Re: ADP or MDB - which is a better front end for SQL Server?
- References:
- Re: ADP or MDB - which is a better front end for SQL Server?
- From: Alex White MCDBA MCSE
- Re: ADP or MDB - which is a better front end for SQL Server?
- Prev by Date: Re: ADP in a multi user environment
- Next by Date: Re: Date in SQL Server
- Previous by thread: Re: ADP or MDB - which is a better front end for SQL Server?
- Next by thread: Re: ADP or MDB - which is a better front end for SQL Server?
- Index(es):
Relevant Pages
|
