School Lunch is available in three configurations: single-user, multi-user and multi-school. All versions of School Lunch are licensed on a per school/cafeteria basis. Each school requires a separate license whether operated as a single-school, multi-user or multi-school system. Current licensees receive the most current version of the program, maintenance updates if any throughout the year and free tech support through end of June of the licensed school year.
Single-user versions can only be used on one computer at a time. Many schools have successfully run the program at the lunch room and the office from a common server, but only one user at a time.
The multi-user program allows many computers to connect in a single school. Office personal and lunchroom staff can work on the system at the same time, answering parent's questions or making deposits. Multiple lines may run at the lunchroom at the same time making student processing go much faster. Computers are connected via a local area network in the school. All computers that run School Lunch will need to connect to the CubeSQL database server.
The multi-school system works just like the multi-user system but is designed for small districts that wish to connect up to six schools to the same database. This works great for schools that wish to take advantage of the School Lunch family account. All family money may be deposited in a single family account and used by students in any school on the system that belong to the family account. Reports can be printed at the school or on a district level. Multiple users can work simultaneously at each school. All computers that run School Lunch will need to connect to the CubeSQL database server.
An SQL database server is a computer program that resides on a computer on your network that allows computers in different locations to connect to the School Lunch data file. This allows users in different locations to access the same information. The best scenario is to have the server on a computer that will be left on most, if not all of the time.
The Rodlan School Lunch program uses a SQL database server that allows multiple computers to connect to the same School Lunch database via the multi-user program or the multi-school program.
Advantages of the SQLServer Database Server:
Things to Consider:
CubeSQL server is available from SQLabs. A free version is available that allows up to three connections. To go beyond three connections requires purchasing the server directly from http://www.sqlabs.com/cubesql.php
Setting up your CubeSQL database server is really quite easy. The process is a little backwards, so read through all instructions before you begin, and make sure that you understand the steps.
Create a group with the Username: rodlan and a password: schoollunch. This allows School Lunch to connect to and make changes to the database.
Do not remove any of these files from the School Lunch folder, or School Lunch may not function properly.
REGISTRATION FILE: The registration file is simply a piece of text code, that tells School Lunch how to function on that particular computer (i.e. what functions and commands are allowed by the user.)
When launching School Lunch, the following message will appear: The 'host' computer (with the Cube server on it) will use this connect information in the example. This 'connect script' allows School Lunch to talk to the server and share information with the other computers that are using School Lunch. As for the remaining computers, they will need use the host computer's static IP address in their connect script setup, along with port 4430. Finish installation with your particular setup below.
Copy the School Lunch folder from the server computer, on to the remaining computers. Now, each computer running school lunch should have a School Lunch folder that contains the following:
Do not remove any of these files from the School Lunch folder, or School Lunch may not function properly. When these computers launch the School Lunch application, they will also receive the Connect Script message box. The IP address of the 'host' or server computer, will need to be entered here, along with port 4430.
Copy the School Lunch folder from the server computer, on to the remaining computers. Now, each computer running school lunch should have a School Lunch folder that contains the following:
Take the registration file out for the time being, because each school will receive their own registration file.
When these computers launch the School Lunch application, they will also receive the Connect Script message box. The IP address of the 'host' or server computer, will need to be entered here, along with port 4430.
Every school will receive a separate registration file from Rodlan. For example 'School 1' will place their registration file into all of the School Lunch folders on all of the computers running School Lunch, at that particular school. Multi-school users will also receive a District registration file. This is basically the administration file, that goes onto the computers of the individuals that are allowed to make the executive decisions for the district/schools.