A friend has the WORST software architecture situation in the world.
I was wondering if anyone could help me walk him through it.

He has a business logic engine for mapping 3-d data to the screen
written in C++.

His clients want him to create a thin-client, preferably a web-based
tool on a CD-Rom.  This can have an access database on the backend.
The clients want to deliver this product in 2009.  So there will be a
cd rom with a one-click install that will utilize the 3d mapping
engine in C++.

He must then take the same code and implement it on a server in 2010.
The same front-end and the same middleware must be put on a server.
The clients do not have a server now.

As you can imagine this is a noncommercial product.  The above
requirements cannot change unless we can positively prove they won't
work.

We are looking into how to architect something like this.  Any tips or
tricks?

thanks!