After preparing about 600 lines of ADOX code used to set up my database, I
came to the discovery that setting some adox
column.properties['Default'].Value seemed to be ignored.  When I afterward
opened the database in Access there were NO defaults set anywhere!

This was confirmed by Microsoft's knowledge base article:
http://support.microsoft.com/support/kb/articles/Q255/9/97.ASP

       When attempting to set the Default property of an ADOX
       column object using the Microsoft Jet   4.0 provider, the value
       is not set. No error message is generated. Trying to change
       the Default property removes any existing Default value already
       in place.

       NOTE: This behavior only occurs under ADO 2.5.
                     ADO 2.1 works as expected.

However, I found a work around by using a TAdoCommand to send the SQL:
'ALTER TABLE SomeTable ALTER SomeColumn SET DEFAULT SomeDefault'

I can't believe this major flaw in ADOX exists (especially since it worked
in 2.1)!!!  YOU CAN'T USE ADOX 2.5 TO SET A DEFAULT VALUE FOR A COLUMN IN AN
ACCESS 2000 DATABASE!!!  There I feel better.