> Ah, but when you delete records Access uses the deleted > space again AFAIK. So, the records that are physically > in the DB may not be in the order that you think...
This, unfortunately, isn't the case. Access doesn't reuse deleted space, which is why you really don't want to use Access to store, say, CF's Client variables - you can have a 2 Gb database file with 100 records in it! (true story!) > Even when you view the database in Access there is some > kind of ordering rule in effect...it's just behind the > scenes so that when you view the table in Access, Access > is probably ordering it by the first column even though > the records are not in that order physically. This is true for any database, I think - and typically, the ordering rule is "show records using the order of the clustered index". Of course, this corresponds to the actual physical ordering of the records, which itself may not correspond to the order in which they're created, but the order of the values in the primary key (which tends to be where the clustered index is placed, even though it's often best used on another field in the case of surrogate primary keys). Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
