If you want to copy business units between different databases, you must run SunSystems within the target database. You must then specify the source database by entering its name in the Source SQL Database field.

Source Business Unit
Enter the code of the business unit you want to copy. It must be a valid and complete business unit both in terms of its business details and its database structure, otherwise attempting to copy it could result in run-time failures. If the specified business unit is in another database, then it must be for the same version of SunSystems.
Target Business Unit
Enter the code of the target business unit.

Suppress Transactions
By default this check box is checked to stop the copying of business transactions tables and allows you to duplicate the static data details of business units. If this check box is unchecked all transaction details are also copied.

Copy SFL’s
By default this is set to allow any Form details that have been set up for the source business unit to be replicated for the target business unit. The copy process searches for SFLs that have been set up specifically for the source business unit. These can be set up to include other business units, but those set up for 'all' business units are ignored.

For 'same' ServerFiles copying, the target business unit is included in the list of specified business units for those SFLs affected.

For ‘across’ ServerFiles copying, the SFL is replicated in the target’s ServerFiles folder with only the source business unit code specified. Where the SFL already exists in the target ServerFiles folder, the existing specified business unit codes are retained.  This process does not include the actual forms (.rfx files), which have to be recompiled manually.

If the ServerFiles folder is changed, then it must include the full directory path details, for example, D:\SUN5\ServerFiles\. If the ServerFiles folder is on another machine then it must be made a ‘shared’ file and specified with the usual format \\OtherMachine\ServerFiles\.

If installed properly SunSystems Session Manager has Administrative rights to the local machine. If not, BUCPY may not locate the SFL folder when attempting to access a server folder on another machine. In this case you need to do the following:

Source SFL Folder
By default this is set to the ServerFiles folder for the instance of SunSystems that you are running in. You can change this to the ServerFiles folder of another copy of SunSystems which may be necessary for inter database/server copying.