Compared to many other programs, FoodWorks is very user-friendly not only with respect to ease of use, but to ease of installation and maintenance. If installation instructions are followed, very few technical issues ever arise. However, answers to common technical support questions are listed below. Select a question by clicking on the button to its left. Or, scroll down to review all of the questions and answers. If you don't find your question in the list, click here to send an email to Support. We will be happy to assist you.
Every FoodWorks installation must be registered within 30 days of installation. This helps us to minimize illegal usage of our intellectual property and helps to keep the fees you pay as low as possible. This works so well that we have not raised prices in more than 10 years. When you register your FoodWorks software, you will submit a "registration code number" that your computer will generate and display on the Registration Reminder window (which appears each time you start FoodWorks until the time you complete the final registration). The Registration Reminder window will contain instructions as to how to complete the registration. After you submit the information to The Nutrition Company, you will receive a "key code number" and instructions on how to enter it into FoodWorks. After entering the key code number, a software key will be placed on the computer and your FoodWorks software will be available for continuous use.
NOTE: Installing software keys affects your computer operating system. You must have "administrator" rights on your computer to complete this process. If you are installing FoodWorks on a computer you purchased and own, you almost certainly have sufficient rights. However, if your computer is owned by a hospital, government agency, or corporation, you may have limited rights that will prevent you from performing administrative functions such as this.
If your pre-registration period expires and you are denied access to FoodWorks, registering and entering a key code number will restore normal operation.
Key code numbers are "triggers" that cause FoodWorks to install a software key on your computer. After you have used your key code, it will no longer be needed, so you don't need to file it. Should you need to install FoodWorks on a new computer in the future, that computer will generate a new registration code number. Thus, you will need a new key code number. Simply contact The Nutrition Company to submit the new registration code number and we will provide you with the correct new key code.
You most likely do not have sufficient rights on your computer to perform the registration process. If you must log on to your computer with a user name and password, you most likely have limited rights. This is common on computers owned by hospitals and other institutions. You must find an "administrator" (such as your IT representative) to perform the registration for you. They will need to sign on to your computer as an "administrator" and then run FoodWorks and make a note of the "registration code number" that appears on the Registration Reminder window. They must then run FoodWorks again and make sure that the number remains the same. Then, follow the instructions in the Registration Reminder window to submit the registration information to The Nutrition Company. When you receive the key code number, they will need to sign on again and enter it into FoodWorks according to the instructions that accompany it. They also must make certain that you, the user, are given "full" rights in the folder where the FoodWorks application is stored. You will then be able to use FoodWorks continuously and normally.
The answer to this question is identical to the answer for the question directly above. Use that solution to correct this issue.
Your user does not have sufficient rights in the folder where the FoodWorks application is stored. If you give the user full rights in that folder, the error will almost certainly disappear.
If you are installing FoodWorks in a school for student use, we recommend installing the application in a location where you can give your student users full rights in the application folder. After you have installed and tested FoodWorks at the student log-in with student rights, make a backup of the application folder to a safe location. That way, if damage occurs to the installation you can easily restore it by simply copying the backup into the normal installation location.
Normally, in a perfect world, a FoodWorks software key never needs to be replaced or maintained, and this is usually true for an individual user. However, in institutional settings, such as hospitals, computers are routinely updated and maintained by IT departments who are responsible for their content and security. During such maintenance, utilities may be run on your computer that clear files that the utility believes are "unused". On rare occasions, this may include index files for software keys. If your key is deleted from your computer, your FoodWorks software will think that you have just now installed it and will begin requesting a new registration. In even rarer cases, the key disruption may be severe enough to deny you access to FoodWorks. In either case, the solution is to contact The Nutrition Company and obtain a new key code number. Installing a new key will immediately restore FoodWorks to normal operation.
If your FoodWorks key has been disrupted more than once, contact Support for help with strategies to eliminate the problem.
NOTE that, depending on your rights on your computer, you may need an IT representative to perform the registration process for you. Click here to go to the question "What is final license registration and how does it work?" for more information on this issue. The discussion will appear at the top of this page.
FoodWorks is fully functional on computers running Microsoft Vista or Windows 7. However, there are two known issues that may affect your installation of FoodWorks under these operating systems:
Some users may experience one or more registration messages during installation of the FoodWorks software. If so, a message will appear stating that a system file will not be registered. If this message appears during your installation, click the “IGNORE” button and let the installation proceed. A second and possibly third message may also appear referring to the same issue. Click the “IGNORE” button for these messages as well. The FoodWorks installation will then complete normally and your FoodWorks software will be ready for you to use.
Also, in some versions of Vista, the FoodWorks icon may not be added to the programs list on the Start button menu. If this happens, you can easily create a desktop shortcut for FoodWorks. To do this, select “Computer” from the Start button menu. Double-click “Local drive C:”, then locate and double-click the “Program Files” folder. Inside the Program Files folder, locate and double-click the “FWorks...” folder. Locate the FoodWorks application's red and yellow chili pepper icon and right-click on it. A pop-up menu will appear. Choose “Send to” from the menu and then choose “Desktop” from the sub-menu. This will create a FoodWorks desktop icon for you to use.
No. FoodWorks requires no special software of any kind to run properly.
That depends on your Macintosh computer. While FoodWorks is guaranteed to function only with Windows operating systems on PCs, many Macintosh owners are successfully using FoodWorks on Macintosh computers that have Windows software solutions installed (such as Parallels, Boot Camp, or Fusion). Currently, the best solution for running FoodWorks on an Intel-based Macintosh is CrossOver Mac from CodeWeavers. You can find links to CodeWeavers and to other Macintosh Windows solutions on the FoodWorks technical specifications page. Click here to go there.
You can also contact your Macintosh software reseller to learn about Windows emulation software. If you have specific questions about using FoodWorks on your Macintosh, contact Nutrition Company Customer Service. Click here to see Nutrition Company contact options.
Installing FoodWorks on a network server for local area network access requires an Unlimited Site License. Your unlimited site license materials will include detailed instructions about how to install and configure FoodWorks on your network server. The FoodWorks software system includes all of the features necessary to install it on a server or on a stand-alone computer. However, only under an unlimited site license can the network installation features be invoked. Click here to go to the information about FoodWorks licenses.
FoodWorks can be installed and run in almost any network architecture. Features include database relocation so that you can move the food/nutrient data files into a location where they are easily secured, shared, or backed up. If your network gives your users a "virtual drive" that is a drive letter pointing to a network resource where they can place files related to their projects and work, you can configure FoodWorks to take advantage of that.
The installation instructions supplied with your unlimited site license outline all of the steps necessary to successfully install and configure FoodWorks on your network. If you do not have these instructions, contact Support, provide your FoodWorks license serial number, and request a copy to be emailed to you. Technical Support has more than a decade of experience helping IT professionals install FoodWorks on networks. If you have specific questions about installations on your network, contact Support (click here to send an email).
That depends on how you are going to do the deployment. Note that any deployment beyond seven computers requires an unlimited site license. Click here to go to the information about FoodWorks licenses.
If you are using "cloning" software, such as Ghost, you will install FoodWorks on a "master" computer along with other software that is to be made available to lab users. The procedure is to install FoodWorks on the "master" computer and then complete the final license registration BEFORE doing the cloning to the lab computers. By completing the registration on the "master" computer, the registration will automatically be carried onto the lab computers, thus saving you a lot of work.
If you are doing individual stand-alone installations on your lab computers, then you can use the instructions supplied with your unlimited site license to bypass the need to register individual computers using the "registration code / key code" method. No matter which deployment method you choose, you can contact Support for assistance with any broad-deployment issues.
The Nutrition Company recommends that after you complete the setup and testing of FoodWorks, you make a back-up of the application folder, especially if you deploy FoodWorks to computers that will be used by students. In the event that a lab computer's installation is damaged, you may be able to repair a problem simply by overwriting the damaged folder with the backup.
The most likely issue is that you do not have sufficient rights in the folder where the FoodWorks application is stored. If your IT representative gives you full rights in that folder, the error will almost certainly disappear.
This type of error has multiple possible causes, but by far, the most common scenario is that you have installed FoodWorks on a network server and this error is occurring on a workstation that is trying to access it. Sometimes this error will affect only some workstations while others are unaffected. The cause of this situation is access to dependency files. The dependency files connect FoodWorks to the operating system and are supplied by Microsoft to be distributed along with FoodWorks. When FoodWorks is installed on a network server, the dependency files are normally installed on the server along with the FoodWorks software. However, if FoodWorks was installed to the server from a workstation, it is possible that the dependency files were installed on the workstation. In this case, they are not visible to other workstation, thus causing this error.
The solution is to install FoodWorks on the server from the server itself, not from a workstation.
If you received FoodWorks on a CD, you can copy the image of the CD onto the server’s main drive and then execute the SETUP.EXE file in the root directory of the CD image to complete the installation. The workstations should then be able to run FoodWorks normally.
If you received FoodWorks via download, a folder called "FWn setup" (where n is the number of your version of FoodWorks) was created when the downloaded file was extracted. This folder is the equivalent of a FoodWorks CD. Copy it onto the server’s main drive and then execute the SETUP.EXE file in the root of the folder to complete the installation. The workstations should then be able to run FoodWorks normally.
If this does not clear the error, then your network is configured in such a way as to prohibit the affected workstations from accessing server-based dependencies. You can then use a second method to clear the issue. On the FoodWorks CD (or in the "FWn setup" folder), you will find a folder called “Dependency Setup”. Insert the CD into the workstation CD drive (or copy the "FWn setup" folder onto the workstation's hard disk drive) and execute the SETUP.EXE file found inside the Dependency Setup folder. This will install the system dependencies on the workstation, after which the FoodWorks software will begin to function normally. If your workstations are not equipped with CD drives, you can copy the folder to the workstation from the server via the network, or use a USB memory device to transfer the folder to the workstation.
If you continue to have problems with the network installation, contact Support for specific assistance (click here to send an email).
The very first thing to do is check to be sure that all users have "full" rights in the folder where the FoodWorks application is stored, regardless of where that folder is located. If you can sign on as "administrator" and FoodWorks runs properly, and then sign on as a user and it does not run, then the problem is user rights.
If setting the user's rights does not clear the error, then the second most likely cause is access to dependency files. This issue can be resolved by following the instructions in the answer to the question located immediately above this one (click here to go there).
The rule to remember in this situation is this: If FoodWorks is running on some workstations and not on others, then your installation is valid. The problem lies either with the configuration of the workstation or the user's rights. However, in very rare circumstances there may be other obscure sources. If you have exhausted the solutions listed above, contact Support for assistance (click here to send an email).
This is a simple matter that happens every day. Begin by installing FoodWorks on the new computer using your existing FoodWorks CD-ROM or your backup of the FoodWorks download setup folder (called "FWn setup" where n is the number of your version of FoodWorks). Use the original installation instructions to complete the installation. Make sure your end user has full rights in the application folder (where the FoodWorks application is stored).
Next, you will need to run FoodWorks and enter your license serial number when prompted. You also will need to complete a final license registration because the new computer does not have a software key installed (there is no charge for this). Follow the instructions on the Registration Reminder window when it appears.
At this point, your new FoodWorks installation is ready to use. Files you created using FoodWorks on your old computer can be copied onto the new computer and opened using FoodWorks. However, there may be one additional step to complete. If foods were added to the "user database" and/or "favorites list" on the old installation of FoodWorks, then those files will need to be copied onto the new computer. In a normal installation, the files are found on the old computer in C: drive > Program Files folder > FWorksn folder (where n is the number of your version of FoodWorks). If your FoodWorks installation was re-directed to an alternate location at installation, you will need to find that location by searching for the files using your Windows "file search" function. The names of the files are:
You can use any method available to copy these six files from the old computer into the same folder on the new computer. You will need to overwrite any files of the same name that already exist on the new computer. When you have completed the copy, any foods that were added to the user database on the old computer will be present on the new one. The favorites list will be intact, and the user's settings and last project will be present when FoodWorks is started.
Of course, if you have any other questions about moving FoodWorks to a new computer, you can contact Support for assistance (click here to send an email).