Option to store embedded description objects on the file System.
Always a bad idea to store binary objects in a DB. It is the reason why our DB went from 2g to 32g in 3 years. It makes the DB bloated and hard to manage during backups, upgrades and the like. The objects should be external to the DB so they can be managed separately.
A best practice is to either provide the URL directly to the file in a shared environment like SharePoint or create a Reference vs. including the object as Description content. It is recommended that the file URL be in a shared location vs. being stored on the client machine to ensure maximum collaboration.
Sometimes images are an integral part of the requirement and have to be displayed in the description. Do you see a MSWORD doc using a URL to a shared environment? That is the paradigm most users think of. Your last sentence about maximun collaboration seems a bit of a canned response. I had the same response 12 years ago on this topic. The images and graphics embedded in the description field can add up. It is not uncommon for us to have over 1 gig of images in a single Caliber project.
Jason Aderhold commented
I'm a little confused. You guys added the feature to allow embedded objects into descriptions and then say the best practice is to not use it? Solving DB bloat is what I am after and since deleting requirements doesn't clean the DB of these pictures and objects we are stuck having the objects in our DB forever. Either store those objects on the file system or give us a way to truely remove the objects from the DB.