shaunw wrote:In most cases it shouldn't be a problem.
I followed the steps you included in a the previous link. It is still creating a completely new database after I transferred over my old database, and edited the SALT= in the ini.php file.. The steps listed below is how I followed it, and it just created a new database.
On the source computer (the one that currently has TimeTrex installed on it):
1. In the TimeTrex directory, execute backup_database.bat to dump the latest copy of your database to a .SQL file.
2. Rename the newest timetrex_database_<DATE>.sql file to timetrex_database.sql.
3. Copy timetrex_database.sql and timetrex.ini.php to a temporary directory on the destination computer, for example c:\temp
On the destination computer:
1. Edit the timetrex_database.sql and delete the first 97 lines, or everything from the top of the file to just above the first line that contains:
\connect timetrex
Make sure the above line still exists in the file.
2. Install a fresh copy of the latest version of TimeTrex, however pause on the final step of the installation procedure where it asks you to launch the web browser to complete the installation.
3. Go to your “Start” button and select the “Run” option, type in:
cmd
4. In the command prompt window, navigate to the TimeTrex directory:
cd c:\timetrex
5. Restore timetrex_database.sql to the new TimeTrex database with the following command:
restore_database.bat c:\temp\timetrex_database.sql
6. Edit c:\temp\timetrex.ini.php, and copy the line that starts with salt= to the new c:\timetrex\timetrex.ini.php
7. Copy the entire c:\timetrex\storage directory from the source computer to the same location on the destination computer.
8. Go back to the TimeTrex installer and complete the installation process, which will be referred to by the installer as an upgrade from now on.
9. Once the installation is complete, confirm that you can login to it with your existing username/password, then disable or uninstall TimeTrex from the source computer to prevent employees from accidentally accessing the wrong instance.
How do I correct this?