Question: I have intermediate knowledge of flash and actionscript, but I have never done 3D animations in flash. Now I'm into a project that requires me to make a menu that looks like a DNA molecule, with each atom being a link to something. I want to make the DNA molecule looks like a real rotating 3D object. Can anyone help me out how can I implement this? Can there be any hack (like using videos of rotating DNA molecule, etc) ???

Answer: 
A database schema should be designed on paper or with an [ERD](http://en.wikipedia.org/wiki/Entity-relationship_model) tool. 

It should be implemented in the database.

Are you thinking about [ORMs](http://en.wikipedia.org/wiki/Object-relational_mapping) like [Entity Framework](http://msdn.microsoft.com/en-us/library/aa697427%28VS.80%29.aspx) that let you use code to generate the database?

Personally, I would rather think through my design on paper before committing it to a DB myself. I would be happy to use an ORM or class generator from this DB later on.
ORMs have their place, that place is NOT database design. There are many considerations in designing a database that need to be thought through not automatically generated no matter how appealing the idea of not thinking about design might be. There are often many things that need to be considered that have nothing to do with the application, things like data integrity, reporting, audit tables and data imports. Using an ORM to create a database that looks like an object model may not be the best design for performance and may not have the the things you really need in terms of data integrity. Remember even if you think nothing except the application will touch the database ever, this is not true. At some point the data base will need to have someone do a major data revision (to fix a problem) that is done directly on the database not through the application. At somepoint you are going to need need to import a million records from some other company you just bought and are goping to need an ETL process outside teh application. Putting all your hopes and dreams for the database (as well as your data integrity rules) is short-sighted.