There are now two available options for accessing The Food Processor and Genesis R&D in the cloud.
Option 1: Online Subscription
ESHA now offers a cloud-hosted subscription option for both The Food Processor and Genesis R&D. To access the program, you would launch the application from a website instead of installing the software locally on your computer. If you are interested in this option, you can contact ESHA's sales department by email at email@example.com, by phone at 800-659-3742 x2, or by using the chat box this page.
For hosting the database on a virtual server and running the client from that server:
Since you won't have to set up a SQL connection between the host server and the clients, this setup is much easier than running the client from your workstation. It also requires more from your virtual server, so it might cost more to run this way.
If you only have a single user, you can install the application as the "stand alone" install type on the server. (Warning: Due to the limitations of SQL Server localdb, you can only have one user access the database at a time with this install type, even if you have a multi-user license). If you have multiple users you would like to have access the application at once, you will need to use the "Network/Shared" install type.
Once you have the application and database setup on the server, you can just remote desktop into the server and run the application, no additional setup required.
For hosting the database on a virtual server, but running the client from your local workstations:
This will focus on Microsoft Azure as the host service, but others could be used.
This will focus on hosting the database on a virtual server. With Food Processor v11.x or Genesis v11.x, you are able to host the database on an Azure SQL Server instance as well. More information on that will be available soon.
Here is the setup guide from Microsoft for setting up Microsoft Azure:
Overall you must:
Create a Virtual Machine on Azure and install Food Processor/Genesis (or install an instance of SQL Server)
Create a TCP endpoint for the virtual machine. To do this, you need to go into the SQL Server Configuration Manager, expand "SQL Server Network Configuration", click on the instance you installed, right click on the "TCP/IP" protocol and click Properties. Under the IP Addresses tab, scroll to the bottom. Under IPAll there is a TCP Dynamic Ports number, this is your Private Port for the TCP endpoint. The Public Port for the endpoint is any number you make it.
Make sure the SQL Browser and instance are both running. Also, make sure that TCP/IP is enabled in Configuration Manager
Make sure you have opened this same port in the firewall on the VM. Also, add the instance and sql browser to the firewall exemptions.
You must use SQL Authentication, Windows will not work.
When connecting to the database, use "servername,PrivatePort\instance" example: tutorialtestVM.cloudapp.net,57500\esha