Think i got it working... We had wanted to keep out LanSweeper 3.5.2 server and database still running until I know that the new server is up and running. Also by having the 4.0 server start with a clean database is nice also.
I was able to stop the service on the 3.5.2 server, rename the database, then I edited two CONFIG files:
Lansweeperservice.exe.config
web.config
with the new database name (renamed it LanSweeper352). Then restarted the service. Appears to be working correctly.
Thanks,
Claud