This article will cover:
- Installing your program on a new computer
- Backing up your database
- Restoring your database
- Re-adding users
- Additional steps for a network setup
Installing your program on a new computer
Install your program on the new machine using the installation instructions appropriate for your situation.
Note: If you are using your own instance of SQL Server this isn't needed.
Backing up your database
1. Exit the ESHA software from all computers.
2. Do one of the following:
On the computer that currently houses your database, click Start/ESHA/Database Utility.
OR
Go to Start and start typing 'Database Utility' to find and open Database Utility.
3. On the menu, click Database/Backup.
4. Select a location and name for the backup.
5. Move the physical file (*.bak) to the new machine.
Restoring your database (on the new computer)
1. Exit the ESHA software from all computers.
2. Make sure your .bak (backup) file is in an easy-to-access location.
2. On the new computer, do one of the following:
On the computer that currently houses your database, click Start/ESHA/Database Utility.
OR
Go to Start and start typing 'Database Utility' to find and open Database Utility.
3. On the menu, click Database/Restore.
4. Locate & highlight the .bak file from which you wish to restore.
5. Click OK.
6. After the Restore completes, there is likely need to (re)add your login as a valid user.
7. Still in Database Utility, click Users / Manage.
8. Click New.
9. If needed, change the login name to the proper username of the user who will need to run the software. Often this is the name that appears by default.
10. Click Create.
11. Close Database Utility and test the application to see if your data is present.
After the above, the new computer will have the same database as the old. If you need to update the database, follow these instructions.
Re-adding users
On the new computer, you will need to re-add any users of the program. Even though each user is already in the list, whenever a database changes servers, the users should be re-added to the database. This document should guide you through this. This scenario may also apply to a singular, local installation on a new machine -- particularly under Windows 7.
Additional steps
If this is a setup such that the database will be shared and accessed by other computers, you may need to configure the Windows Firewall (if enabled).
Configuring the .INI file
Also, for a network setup, if you have the program installed locally for each user, you must change the configuration setting, specifically the .INI (Genesissql.ini or Foodprosql.ini) file.
- This file is found here: C:\Program Files (x86)\Esha Research\FoodproSQL\
- Or here: c:\Users\[UserProfile]\AppData\Local\VirtualStore\Program Files\Esha Research\FoodproSQL
- Copy the ini file to the Desktop or other folder.
- Open this file in a text editor.
- Change the ServerName= line to point to the appropriate SQL Server (new computer).
- You may also need to edit the DBConnectionString= line as well.
- Save and exit the .ini file.
- Copy and replace the edited ini file back to the C:\Program Files (x86)\Esha Research\FoodproSQL folder
- Open Food Processor. If no errors, check the Server Name by selecting "About" on the Home tab
Comments
0 comments
Please sign in to leave a comment.