What about Security?
"This is all well and good," you say, "but what about security? We don't want to let anyone request a report for someone's genealogy just because they have the distributor number!"
Not to worry…
That's where a security layer comes in. Since you are going to need some form of CGI program to accept information from a web page on your site, call the treeripper, then send the treeripper's response back to the browser, this CGI can also act as the security layer.
Our Security System
The security layer can be as complex as you like. We have created quite a sophisticated security layer, and I don't personally know anyone that could crack it (including myself).
This system works on a password lookup table. When you export your master database, you would also export an access file. This is a file which contains a user name, password, and distributor number for each person who will be allowed to obtain a genealogy report.
Logging In
When someone wants to get their genealogy, they enter their user name and password into a form on a webpage. These two pieces of information are handed off to the security layer, which looks up the user name in the password list, and then compares the password given with the password in the file.
If the passwords match, the security layer then takes the distributor number for this lookup table, and passes it to the treeripper. Of course, if the password is incorrect, the security layer will just send a message back to the browser saying that the password was entered incorrectly, and it won't do anything else.