simply put:
 
you will install the Pervasive Client Server on your server, DO NOT install DBA.
 
once the server is on the Network, just Copy the ENTIRE DBAMFG directory on your Host computer to the Server.
 
set up your share point. change your existing mapped drive that your users are using for DBA, to point to the server.  
 
ready to rock and roll.
 
now. point 1. new server, 2003 sbs. i reccommend that if you are NOT already on pervasive 9, that you upgrade to that version. Perv 9 was written to support server 2003. perv 2000i was not. although some users do and have used perv 2000i on a 2003 server. better to install the correct tool for the correct job.
 
point 2. if you do upgrade your pervasive, then you also have to upgrade the clients. your cost is on the engine, plus your time.
 
point 3. your copy on the old host computer is now a backup copy. you might want to rename it with today's date, like DBAMFG 062206 , so that no one accidently starts it up and enters data into it.
 
i'm sure there will be other suggestions.
 
dave

Quote from dameng   on 06/22/06 at 18:14:27:

I would suggest, instead, once the new setup is running and backed up, delete the original completely. To have live backups of old data, use the Copy Company function in UT-I after the books are "closed" each year - use a Company Code that corresponds to the year closed. That way it's very easy to go back in time. No need to try and fool DBA into using old data by changing path setups and who knows what else.