If you're using SQL Server 2000 then you have a "Save as..." option that will allow you to save your code to a Visual Basic .bas file
If you are using SQL Server 7.0, there is a utility provided on the SQL Server CD itself. (I am uncertain if this utility is installed/copied to your system during client tools installation but its definitely on the CD itself.) Do a search on the CD for ScriptPkg.exe - it should be a self-extracting zip file. Running a DTS package through this little VB app will create a notepad document that is the DTS package itself scripted out in VB code. (Im pretty certain it is ScriptPkg.exe but also try searching for anything with Pkg - that part I am certain about!)
There are notes included with this zipped file that will help guide you along. Its not 100% but pretty close to it and is now implemented in SQL Server 2000. The known bugs are reported in little Readme.txt files. For instance, the scriptPkg.vbp creates one gigantic routine. VB has a limitation in the amount of lines a module can hold. So if your package is rather lenghty - you have to spend the time to split up the code into distinct modules.
Good luck and I hope this helps or what you are looking for.
Jim