Re: Duplicate Values Question

My understanding is that compatibility with Sharepoint drove most of what
happened with the first release of ACE. The MVP community was generally
upset with the "enhanced" datatypes and the disappearance of user level
security. Many fixes were made to the navigation pane between when we first
saw the demo of A2007 and when it was finally released due to our comments.
The problem was that so many people complained about ULS that the team just
got rid of it thinking that no one wanted to use it. Of course they missed
the point of the complaints. The Nav Pain (SIC) replaces some of the object
protection for a final database but it is at a much higher level than ULS.

"Jamie Collins" <jamiecollins@xxxxxxxxxx> wrote in message
news:77ab5e4e-b1da-4989-bca7-e313b92b975e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 23, 3:27 pm, "Pat Hartman" <please no em...@xxxxxxx> wrote:
Think of it as the difference between "the best possible
solution" and "the best solution possible".

Nice one :)

I have high hopes for Jet (now called ACE, I think) now that the Access
team
has taken over development from the SQL Server team. I am hoping we'll
see
some real improvements in functionality and stability. The SQL Server
team
thought of Jet as a toy and a competitor so they were not inclined to
keep
it current. They totally missed the point of Access as a RAD tool and a
complement to SQL Server.

As an MVP you may have the benefit of some inside information but from
here on the outside things look the complete opposite. Cast you mind
back to Access 2000, the last time engine had a major release. Jet 4.0
had significant new functionality:

Description of the new features that are included in Microsoft Jet 4.0
http://support.microsoft.com/kb/275561

My favourites are the DECIMAL and NCHAR data types, truly table-level
CHECK constraints and improved SQL DDL syntax. IMO the SQL Server team
did a great job.

On the flip side, it seems to me that Access 2000 has gone down in
history as a big disappointment. Even today, nearly a decade on and
three major releases of Access later, many of the Jet 4.0 features are
still to be properly exposed in the Access user interface: NCHAR,
CHECK constraints, SET NULL referential actions, WITH COMPRESSION data
types, row-level locking, and more. The ACE version of DAO should have
left ADO dead in the water but, again, the majority of the
abovementioned Jet 4.0 functionality remains absent.

As regards the ACE version of the engine, it seems to me that more has
been lost than gained. Did the request for multi-value data types come
from the Access user base? Was it really neglect on the part of the
SQL Server team that caused replication to disappear from Jet? Can a
SQL DBMS without user level security really be taken seriously? In all
truthfulness, the only good thing I've seen in ACE is the fix for the
DECIMAL sort bug.

Jamie.

--




.

Relevant Pages

  • Re: Duplicate Values Question
    ... has taken over development from the SQL Server team. ... thought of Jet as a toy and a competitor so they were not inclined to keep ... still to be properly exposed in the Access user interface: ... As regards the ACE version of the engine, it seems to me that more has ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Calculate days between 2 dates ignoring weekends?
    ... I sometimes compare Jet to SQL Server as an aside ... JamieC on Jet: "If this were Jet... ... 'classes' using the MOD operator" [Note SQL Server has no MOD ...
    (microsoft.public.access.formscoding)
  • Re: Creating a new Access database file (.mdb) in .NET/C#
    ... You definitely need to download my Ebook. ... It can be passed around as a file like JET and backed up in a similar fashion. ... Consider that this database is also fully encryptable--a feature not in JET or in SQL Server until 2008. ... Per the MS product pages, I'm eligible for the Upgrade package, and ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Official Status of SQLServer 2005 ADP
    ... As far back as Access 97, Jet has made every attempt ... to "pass through" every Access query against a linked ODBC datasource. ... ends - DB2, Oracle, and SQL Server among others. ... > solution might be to use ADP. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Calculate days between 2 dates ignoring weekends?
    ... I sometimes compare Jet to SQL Server as an aside ... JamieC on Jet: "If this were Jet... ... 'classes' using the MOD operator" [Note SQL Server has no MOD ...
    (microsoft.public.access.formscoding)