Once a database has been used with Versago, the database name can be changed, but it will take some effort. The databses cannot simply be renamed in SQL as there are internal references in the application that must be updated as well. The process will require a complete reinstallation of Versago, so this situation should be avoided if at all possible.

The most common scenario for renaming databases is when the source databases were named for “test,” and now need to be renamed for production use. In this example we will rename the Versago Common and Versgo Data databases. The current database names are “vgoCommonTest” and “VersagoDataTest” respectively. They will be renamed “vgoCommon” and VersagoData.“

Following are the steps to follow if the renaming needs to be done.

• Be sure you have the installation file for the desired version of Versago.
• Export all objects (reports, forms, etc.) from the current installation.
• Create a SQL backup of the current Versago Common database.
• Create a SQL backup of the current Versago Data database.

• Uninstall Versago using the standard “Uninstall a Program” function from “Programs and Features” in Windows Control Panel.
• Use Windows Explorer to remove the folder “Program Files (x86)\TWBS\Versago.”

• Rename the database(s) to the new name (“vgoCommon” and “VersagoData” in this case). This is done in SQL Server Management Studio.
  • Keep in mind that this will not rename the files associated with this database. In this example they will remain “vgoCommonTest.mdb” & “vgoCommonTest.ldb” and “VersagoDataTest.mdb” & “VersagoDataTest.ldb”in the file system.

• Install Versago following the standard process found here.
  • At the point where you define the Versago database, use the new name of the database defined in the previous step.

* Continue through the installation process as if this is a new installation.

• Once the installation is complete, open Versago. You should be able to login normally. All of your reports, forms, etc. should be in place.

• Create any new database connections that may be needed. For example, if you have reports that are pointed to database “B1_Test” and you will want them to point to “B1_Live,” or you have “VersagoData_Test” that will now become “VersagoData,” define the new connections before the next steps.

• Use the Import process described here using the export file created in the first step above.
• Assign the connections to the new connections created in the previous step.
• Be sure that the “Update existing record with file details” option is selected.
• Check the Summary column on the left to confirm that all items were imported successfully at the end of the import process.
• Logout and log back in to Versago.
• Execute various reports and forms to confirm that the changes are working as expected.

The following SQL commands can be used as further confirmation that the connections have been updated. Check the connection names to be sure the reflect the correct target database. If any of the connections still point to the original database, export the specific objects and reimport it.

For Reports

SELECT
t0.ReportName, t0.CompanyID, t1.CompanyName
FROM twbs_ws_orpt t0
INNER JOIN twbs_ws_ocmp t1 ON t0.CompanyID = t1.CompanyID
ORDER BY t1CompanyName, t0.ReportName

For Forms

 SELECT DISTINCT
t2.FormName, t2.CompanyID, t3.CompanyName
FROM TWBS_WS_FormControls t0
INNER JOIN TWBS_WS_FormSections t1 ON t0.FormSectionID = t1.FormSectionID
INNER JOIN TWBS_WS_FormMaster t2 ON t1.FormID = t2.FormID
INNER JOIN twbs_ws_ocmp t3 ON t2.CompanyID = t3.CompanyID
ORDER BY t3.CompanyName, t2.FormName