princepawn, ++ for bringing up the management viewpoint. I'd have to agree that knowing both APIs would be a sound view.

My argument is that somebody has to be the butterfly that causes the storm halfway 'round the world. I'm sure that sybperl handles what is necessary, but eventually, the port to DBD::Sybase will be considered. That's why I suggest early adoption (in the case where you may have to support legacy code in sybperl until you move entirely to DBD, not in the case where you choose an untested technology to build an enterprise solution on). I'd be interested to see if you agree with me that bucking the trend is worthwhile given that one day, the impossible will be required, and management decides to port to an independent interface to be more flexible.

ALL HAIL BRAK!!!