I completly agree, his question infrenced that he already was thinking about the "other side of the coin" I was just stating that it may be worth while to look at the total cost for a home brew solution. On of the other things that may influence you on comercial product vs home brew is the transition path to new technologies -- many comercial apps will have competitors that offer migration tools to move to their products and new technologies -- on the other hand home brew solutions that have to migrate to new technologies leave your org holding the bag. as a referance here look at all of the legacy home brew systems in the corperate world today, many could have been kept up to date and talking with other current applications by sticking with purchased product. My whole point behind this is that you just have to weigh the whole cost/benefit for a decision like this -- it could go either way depending on the situation and org that you work for.

-Waswas

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.