Design question

Hello,
I am working on an application suite that is largely based on a database
(currently SQL Server, soon to add Oracle). Their current schema update
mechanism is to send scripts to their clients to run through Query Analyzer,
and they are hoping for a better approach. My experience is C++/COM and very
light on DB work, so I want to run this approach by more experienced eyes
before I officially propose it.

In the upgrade application, all of the scripts will be stored as resource
strings, making them difficult to alter (read: mess up). The application
will read the current state of the db (a few tables have version info). If
there are any available upgrade routes, they will be presented to the user.
When the user says go, we make sure the db isn't open, then open a local
transaction. All of the relevant upgrade scripts will be run in the single
local transaction, then we will Commit or Abort depending on the outcome.

Does this sound like the way to go? Are there more effective ways to
accomplish this that I'm not thinking of?

Thanks for any information/advice you can offer.

damon