Lyle Fairfield wrote:
The answer, for Access/Jet the PK determines the (non-maintained)
clustered index, the physical ordering on disk.
From
http://msdn2.microsoft.com/en-us/library/wd9d69b1.aspx
THE CLUSTERED PROPERTY IS IGNORED FOR DATABASES THAT USE THE MICROSOFT
JET DATABASE ENGINE BECAUSE THE JET DATABASE ENGINE DOES NOT SUPPORT
CLUSTERED INDEXES.
No need to shout.
Try reading more widely:
New features in Jet Version 3.0:
http://support.microsoft.com/default.aspx?id=137039
Quote: "Compacting the database now results in the indices being stored
in a clustered-index format. While the clustered index isn't maintained
until the next compact, performance is still improved ... The new
clustered-key compact method is based on the primary key of the table.
New data entered will be in time order."
ACC2000: Defragment and Compact Database to Improve Performance
http://support.microsoft.com/default...b;en-us;209769
Quote: "A disk defragmenter will place all files, including the
database file into contiguous clusters on a hard disk ... If a primary
key exists in the table, compacting re-stores table records into their
Primary Key order. This provides the equivalent of Non-maintained
Clustered Indexes"
I think the phrase 'not supported' is used to convey the fact that in
Jet you cannot specify the clustered index independent of the PRIMARY
KEY as you can in, say, SQL Server. It may just mean that there is no
syntax for CLUSTERED INDEX.
Regardless of what 'not suuported' means, clustered indexes definitely
exist for Jet and PRIMARY KEY is the way to leverage them.
Jamie.
--