Yep, I had considered that; essentially it seems like a large amount of work.
Also, security is maintained based on specific workflow conditions, roles
and many other limitations all handled within my existing ASP.NET application
etc, and I have an existing checkin/checkout structure in place as well as
specific behind-the-scenes functionality tied to checkins/checkouts and
actual Sending of any document. To shift it all over to Sharepoint would be a
large amount of work, and would make it far more complex to handle and give a
larger attack surface for the app.
Very specific rights would be applixcable to each version of each document,
and to try and implement this in Sharepoint with all the above seems like a
large task.
If Sharepoint is the only means of accomplishing this, then so-be-it, I can
keep in mind for later versions of the application, but theres not enough
time to attempt that for our current release schedule. I was hoping there was
some means of simply getting the in-memory binary of the doc at save-time and
saving it back to SQL directly, in the same way as I do it at the moment at
document generation time on the server.

Thanks for your suggestion; if anyone else has any other ideas to add, I am
again happy to hear :)

Thanks
Dave

How would that help in ASP.NET...?