[BCB:1:Backup warning:ECB]
Important: We recommend that your network administrator use these instructions as an example of how to convert your Sage Timeslips database on a single user or multiuser configuration. Following the recommendations in this document may affect the functionality of Sage Timeslips and your database. The network administrator or user making these changes is responsible for any issues that may arise from following these steps.
Important considerations before you convert
- Requirements - Must complete the conversion on the server, Firebird Database requires conversions to be completed on the physical machine that the database resides. If you attempt to initiate a conversion from a workstation that is pointed to your database then you will be prompted to stop and go to your server to begin your conversion.
- Operating System Considerations - Your Database location for your newly converted database as well as all future created databases will not have to be shared or accessible by any network workstation directly. It only needs to be accessible by the server. in a Firebird server, the Sage Timeslips application handles all database info requests from network workstations. By default Firebird will place your all of your databases into the C:\ProgramData directory. This is a Hidden directory in windows that only the server has access to. if you need to see this directory you may need to go into your windows folder view options and mark the option Show hidden files and folders.
Make a backup of your Sage Timeslips Data and keep in safe place before performing the tasks below. You may need to restore this backup in the future to view specific information that may have been changed by preparation for the conversion.
- Data Preparation - The issues listed below may affect when you choose to convert your Sage Timeslips database. Evaluate this list to help you determine when it is best for your company to convert.
- Bills and Statements - During the conversion, A/R payments are normally automatically applied. To reduce possible discrepancies in your aging totals after conversion, Sage Timeslips recommends converting after generating and approving bills and statements.
- Exchange with remote databases - Slips from remote databases should be exchanged before converting to your new version. Due to the differences in databases, you will need to distribute remote databases in the new version to your remote users. Remote users will also need the Sage Timeslips CD to update Sage Timeslips Remote on their computer. (NOTE: Sage Timeslips Remote is only applicable to Sage Timeslips 2011 and older)
- Exchange with any 3rd party applications - Make sure that your linked 3rd party applications are compatible with your new version of Sage Timeslips. Exchange any data with Sage Timeslips before your conversion i.e., eCenter, Amicus, Abacus, TimeMatters, etc.
- Bill Stages - Approve or clear bills from proof or revision for all clients.
- Run the system reports - In your previous version of Sage Timeslips, run the System Reports. Some versions of Sage Timeslips contain: Slip File Check, Client File Check, and Timeslips Database Check. These reports can identify problems in your database. If these reports identify errors, correct the errors before converting.
- Finalize G/L Transfer Register - If you have TAL (Timeslips Accounting Link), print and finalize the G/L Transfer Register.
Single station conversion
Before Converting Close All Other Applications on your workstation - After installing your Sage Timeslips Premium upgrade or single station installation, open your Sage Timeslips application. If this was an upgrade then you should be prompted to convert your database. If this was a brand new installation then you will be prompted to open a Sage Timeslips database. Choose Open an Existing Database and browse to your previous version's database.
- You will be prompted with the Conversion dialog. If you are not prompted then choose Open an Existing Database and in the Files of Type field change the type from main.fdb to main.db and proceed to browse to the location of your Timeslips data you would like to convert. Choose Next.
 - If you agree, then mark I understand that taxes will not automatically be updated and choose Next. This is mandatory and if the choice to not make a backup is made, the conversion will not proceed.
- Sage Timeslips requires a backup to be made prior to starting the conversion. This is mandatory and if the choice to not make a backup is made, the conversion will not proceed.
 - The backup will automatically be named using the date and time stamp for the current date and placed in the Timeslips backup folder located in C:\users\[windows_user_name]\Documents\Timeslips Backups folder. Choose Save and allow the backup to complete.
 - Once the backup is complete your Conversion will begin. Depending on the size of your database this could take several minutes or longer to complete. It is a good idea to leave your machine alone and not open any other applications during this time.
 - Once your conversion completes, it will either be successful or fail. If it has failed click the View Log link in the lower right corner of your conversion window to see where the failure is. You may need to contact support for conversion assistance, so be prepared to have your conversion log on hand when they ask for it. In this scenario, conversion was successful and we can click OK.
 - Sage Timeslips will open to your converted data, take some time to check your database for accuracy and contact support if you notice any changes that are incorrect in data.
Multi-station (Network) upgrade conversion
Before Converting Close All Other Applications on your workstation After installing Sage Timeslips Premium/2017+, open your Sage Timeslips application. If this was an upgrade then you should be prompted to convert your database. If this was a brand new full installation then you will be prompted to open a database. Choose Open an existing database and browse to your previous version database. You will be prompted with the Database Conversion dialog. If you are not prompted, choose Open an existing database and in the Files of Type field change the type from main.fdb to main.db and browse to the location of your Sage Timeslips data you would like to convert. Choose Next.  Due to the new database changes, network installations now require the database to be converted locally. If you are opening this database from a workstation that is pointed to a database that is not local - located on a server or network location that is not physically on your machine - then you will need to exit out of this conversion process and go to the machine where the database is located and start Sage Timeslips Premium to begin the conversion there. If that machine does not have Sage Timeslips Premium installed then you will need to copy that database to the machine that is acting as your Timeslips server and start the conversion by opening Sage Timeslips Premium on that machine and browsing to your data using the open database command. If you are on the Server performing your conversion then use the following steps to complete your network conversion. On this dialog you are presented with your server name and the option to convert and make this database available for the entire network or to convert it to use in a single station scenario. We will choose to make it available to the entire network. You must assign a name to the database. The comments field is not required, however it may be useful in some instances where you would like to give additional detail or explanation. When you are ready, choose Next.  If you agree, then mark I understand that taxes will not automatically be updated and choose Next. This is mandatory and if the choice to not make a backup is made, the conversion will not proceed.  Sage Timeslips requires a backup to be made prior to starting the conversion. This is mandatory and if the choice to not make a backup is made, the conversion will not proceed. The backup will automatically be named using the date and time stamp for the current date and placed in the Timeslips backup folder located in C:\users\[windows_user_name]\Documents\Timeslips Backups folder. Choose Save and allow the backup to complete.  Once the backup is complete, the conversion will begin. Depending on the size of your database this could take several minutes or longer to complete. It is a good idea to leave your machine alone and not open any other applications during this time. Once your conversion completes it will either succeed or fail. If it fails, click the View Log link in the lower right corner of your conversion window to see where the failure is. You may need to contact support for conversion assistance, so be prepared to have your conversion log handy when they ask for it. In this scenario, conversion was successful and we can click OK.  Sage Timeslips Premium will open your converted database. Take some time to check your database for accuracy and contact support if you notice any incorrect data.
Multi-station (Network) new installation conversion
Before Converting Close All Other Applications on your workstation After installing Sage Timeslips Premium/2017+, open your Sage Timeslips application. Choose Open an existing database.  You will see a new Open Database dialog. This dialog only displays Registered Databases, new databases created in Timeslips Premium, databases that have been registered with the TSADMIN tool, or databases converted by Sage Timeslips Premium will appear in this dialog. You need to browse to your prior version database using the 3-dot button tool in the lower right hand corner.  In this Open dialog, you will see any MAIN.FDB or MAIN.DB Database file types by default. Browse to the location of your Sage Timeslips data you would like to convert, select the Main.DB file and choose Open.  Once you choose your database to convert, click OK.  You will be prompted with the Conversion dialog. If you are not prompted then choose Open an Existing Database and in the Files of Type field, change the type from main.fdb to main.db and browse to the location of your Sage Timeslips data you are converting. Choose Next.  Due to the new database change, network installations now require the database to be converted locally. If you are opening this database from a workstation that is pointed to a database that is not local - located on a server or network location that is not physically on your machine - you will need to exit out of this conversion process and go to the machine where the database is located and start Sage Timeslips Premium to begin the conversion there. If that machine does not have Sage Timeslips Premium installed, then you will need to copy that database to the machine that is acting as your Timeslips Premium server and start the conversion by opening Sage Timeslips on that machine and browsing to your data using the open database command. If you are on the Server performing your conversion, then use the following steps to complete your network conversion. On this dialog, you are presented with your Server name and the option to convert and make this Database available for the entire network, or to convert it for use in a single station scenario. We will choose to make it available for the entire network. Give the database a name. The comments field is not required, however it may be useful in some instances where you would like to give additional detail or explanation. When you are ready choose Next.  If you agree, then mark I understand that taxes will not automatically be updated and choose Next. This is mandatory and if the choice to not make a backup is made, the conversion will not proceed.  Sage Timeslips requires a backup to be made prior to starting the conversion. This is mandatory and if the choice to not make a backup is made, the conversion will not proceed.  The backup will automatically be named using the date and time stamp for the current date and placed in the Timeslips backup folder located in C:\users\[windows_user_name]\Documents\Timeslips Backups folder. Choose Save and allow the backup to complete.  Once the backup is complete, the conversion will begin. Depending on the size of your database this could take several minutes or longer to complete. It is a good idea to leave your machine alone and not open any other applications during this time. Once your conversion completes it will either succeed or fail. If it fails, click the View Log link in the lower right corner of your conversion window to see where the failure is. You may need to contact support for conversion assistance, so be prepared to have your conversion log handy when they ask for it. In this scenario, conversion was successful and you should click OK.  Sage Timeslips Premium/2017+ will open your converted database. Take some time to check your database for accuracy and contact support if you notice any incorrect data.
[BCB:167:Chat Timeslips US:ECB]
|