What is WebDNA

WebDNA is a scripting and database system designed to easily build web applications.

WebDNA and BioType

BioType service is a biometric keystroke dynamic system. It will be part of WebDNA 8.5

Download WebDNA

Download WebDNA freeware, try it and register later if you want.

WebDNA resources

The list of all WebDNA instructions.
WebDNA
Software Corporation
Search WebDNA Site
 Menu


HOME


DOWNLOADS


LEARN


EDUCATION


NEWS


COMMUNITY


STORE


SUPPORT


CONTACT

Re: Who is doing sign-ups-got it

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17122
interpreted = N
texte = >>I think I found Ken's examples in the archive about modifying the >>multigroup checker and changing out the user.db. So I will go with Kens >>example over the weekend and see what happens. >> >>Let me try this unless someone has tried this and it does not work > > >Hi Gary, > >I'm not sure what you've found in the archives, so here's a review: > >I've adopted the practice of using a different database -- instead of the >users.db -- for the sites I create for others. This makes it easy for me >to create a drag-and-drop installation for my clients. Each site is >instantly portable when *ALL* the templates and db's for the entire site >are contained within a single folder. > >Here's what I do: > >1- create a new folder for my client's web site >2- create a duplicate of the users.db and rename it access.db >3- create a duplicate of the multigroupchecker file and rename it protect >4- in the protect file, change all occurrences of users.db to access.db >5- place these and all other templates and db's into my client's web site >folder >6- use tags like the following for protecting pages inside my client's web >site: > >[include file=protect&groups=group1,group2,group3] > >By the way, you can add as many additional fields to the access.db as >you need. So if you're registering users and giving them protected access >to certain pages, the access.db is the natural place for their >registration data to be maintained ... :)Bingo, that is the same thing I found in the mail archive search... when I got real smart with my search and put in user.db then I found it. thanks Ken=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== Associated Messages, from the most recent to the oldest:

    
  1. Re: Who is doing sign-ups-got it (Gary Richter 1998)
  2. Re: Who is doing sign-ups-got it (Gil Poulsen 1998)
  3. Re: Who is doing sign-ups-got it (Bob Minor 1998)
  4. Re: Who is doing sign-ups-got it (Kenneth Grome 1998)
  5. Re: Who is doing sign-ups-got it (Gil Poulsen 1998)
  6. Re: Who is doing sign-ups-got it (Britt T. 1998)
  7. Re: Who is doing sign-ups-got it (Brian B. Burton 1998)
  8. Re: Who is doing sign-ups-got it (grichter@panavise.com (Gary Richter) 1998)
  9. Re: Who is doing sign-ups-got it (Kenneth Grome 1998)
  10. Re: Who is doing sign-ups-got it (grichter@panavise.com (Gary Richter) 1998)
>>I think I found Ken's examples in the archive about modifying the >>multigroup checker and changing out the user.db. So I will go with Kens >>example over the weekend and see what happens. >> >>Let me try this unless someone has tried this and it does not work > > >Hi Gary, > >I'm not sure what you've found in the archives, so here's a review: > >I've adopted the practice of using a different database -- instead of the >users.db -- for the sites I create for others. This makes it easy for me >to create a drag-and-drop installation for my clients. Each site is >instantly portable when *ALL* the templates and db's for the entire site >are contained within a single folder. > >Here's what I do: > >1- create a new folder for my client's web site >2- create a duplicate of the users.db and rename it access.db >3- create a duplicate of the multigroupchecker file and rename it protect >4- in the protect file, change all occurrences of users.db to access.db >5- place these and all other templates and db's into my client's web site >folder >6- use tags like the following for protecting pages inside my client's web >site: > >[include file=protect&groups=group1,group2,group3] > >By the way, you can add as many additional fields to the access.db as >you need. So if you're registering users and giving them protected access >to certain pages, the access.db is the natural place for their >registration data to be maintained ... :)Bingo, that is the same thing I found in the mail archive search... when I got real smart with my search and put in user.db then I found it. thanks Ken=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== grichter@panavise.com (Gary Richter)

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] sem_open bugfix for os x version 6.2 (2012) WC Database Format (1997) Formulas.db + Users.db (1997) syntax question, not in online refernce (1997) [WebDNA] filter out the exclaimation point (2017) Spontaneous Errors (2004) Re(2): [WebDNA] mac os for wc 6.0 (2008) Field name-subcategory (1997) changing creator codes (2000) WebDNA's current version? (2003) Re2: AAgghh!! Help, please. SSL strikes again. (1997) writefile and deletefile (1998) ShowNext (1997) Check for OS (2003) X Server (1999) [ot] RH 7.2 WU-FTP Question (2003) A new bug? (1999) Rhapsody? (1997) WebCatalog2 for NT Beta Request (1997) Running 2 two WebCatalog.acgi's (1996)