Basically I just plan to keep a small database on anyone whose site I review for membership, whether they are accepted or not. I'm still working on the precise design, but it's pretty simple. Name, email, SiteTitle, URL, ID#, Notes. I'll leave description and keywords to the member database. IOW, Ringlink will keep the "CurrentMembers" and I'll keep "Contacts" behind the scenes. James S. Huggins (dot com) wrote: > > Understood. Perhaps you would like to suggest ways to expand the > "database" that Ringlink keeps to incorporate such features and > eliminate the need for a separate database. Not a short term solution > for you to be sure, but perhaps a way to expand the functionality long > term. > > James S. Huggins > > -----Original Message----- > Bill Wilson > > Or my plan. I plan to approve sites before I send them to the sign-up > page. Then I'll tell them their Site ID and send them the code. > Their Site ID will be the record number in a database I'm building to > track all members and applicants. Then I'll have data on all current > and former members, and on applicants including the reasons they were > turned down so when they re-apply I'll recognize them. > > > > > > |----------------------------------------------> | Bill Wilson | St. Louis - Boise - Detroit | OB7 |----------------------------------------------> | http://www.buildapage.com | The best spot on the `Net for all your small | business web site hosting and design needs! |----------------------------------------------> | | This is the true joy in life: | | - Being used for a purpose recognized by | yourself as a mighty one, | | - Being thoroughly worn out before you are | thrown on the scrap heap, | | - And being a -force- of nature instead of | a feverish, selfish little clod of | ailments and grievances - complaining | that the world will not devote itself to | making you happy. | | -- George Bernard Shaw | |---------------------------------------------->