Re: [WebDNA] Sort by Row

This WebDNA talk-list message is from

2017


It keeps the original formatting.
numero = 113690
interpreted = N
texte = 1285 --Apple-Mail=_B0F4F810-DC17-4D84-8E1F-BD7ADFCE0B70 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I was thinking the same thing. Probably not a big help or what you want to hear but I would consider = reorganizing this data so that it is properly normalized. For example consider the following field structure SKU, DOW, SH, EH 1000,6,3,5 (Thats a day 6 block for 3 to 5pm) This way you have essentiality the same data and now you can group your = results VERY easily buy Day of the week, start times or endtimes. While it feels like you have more data this way, you actually have a ton = less as in any standard DBS system you are blocking memory for fields = without or without data. And in the way you=E2=80=99re dealing with now = you not only are repeating verbose days over and over (lots more text = data), but also settings placeholder for ~40 fields simply for 3 data = elements. If you really want to do this right I would make the DOW a r_DOW field = where the number relates to a related sku in a day table so that you can = easily adjust spellings or dat abbreviations in Data and not in code. HTH AJ > On Oct 18, 2017, at 4:59 AM, Stuart Tremain = wrote: >=20 > Hi Stephen >=20 > A little bit vague on what you are trying to achieve but: >=20 > You may have to do 7 searches, and then sort the searches by hour for = that day. >=20 > Search for all records =3D Monday sorted by hours >=20 > There could be easier ways to achieve this depending on how you have = set up your db. If you have 40 fields in your db, why not give them a = position number i.e. 01 - 40 and then just sort by position number ? >=20 >=20 >=20 >=20 >=20 > Kind regards >=20 > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 >=20 >=20 >> On 16 Oct 2017, at 15:29, Steve @ Tailored Web Solutions = > = wrote: >>=20 >> I have an html form with 40ish checkboxes for hourly time spans of = each day, which correspond to fields in the database. >> example: FRIDAY_1_3FRIDAY_11_1= FRIDAY_3_5FRIDAY_9_11= MONDAY_1_3MONDAY_11_1= MONDAY_3_5MONDAY_9_11 etc... >> The data in the fields looks like this: onon= on= onon >>=20 >> The customer has asked me to sort the entire db by the days of the = week, then the hours of each day. >> So I thought that if I assigned a number value to each field: 3= 241= 768= 5 >> thought then I might be able to sort by these numbers, but I didn't = know how. >>=20 >> Thanks for asking, >> sfb >>=20 >>=20 >>=20 >>=20 >>=20 >> Stephen Braun >> Tailored Web Solutions >> steve@tailoredwebsolutions.net >> www.tailoredwebsolutions.com >> 315.343.1744 >>=20 >> On Sun, Oct 15, 2017 at 10:58 PM, Brian Fries > wrote: >> Database sorting is always on one or more columns, and effects the = order of the rows returned. >>=20 >> Perhaps you could give us an idea of the problem you are trying to = solve, and we could be of more help. >>=20 >> - Brian >>=20 >>> On Oct 15, 2017, at 7:50 PM, Steve @ Tailored Web Solutions = > = wrote: >>>=20 >>> Yes, I can sort by one or more (vertical) (column) fields >>>=20 >>> Is it possible to sort by (horizontal) rows? >>>=20 >>> Thanks, >>> sfb >>>=20 >>>=20 >>> Stephen Braun >>> Tailored Web Solutions >>> steve@tailoredwebsolutions.net = >>> www.tailoredwebsolutions.com >>> 315.343.1744 >>>=20 >>> On Sun, Oct 15, 2017 at 7:12 PM, Kenneth Grome = > wrote: >>> You can sort by one or more fields. >>>=20 >>> Regards, >>> Kenneth Grome >>> WebDNA Solutions >>> http://www.webdnasolutions.com >>> Web Database Systems and Linux Server Administration >>>=20 >>>=20 >>> On 10/15/2017 11:41 AM, Stephen Braun wrote: >>> > Good Day All, >>> > >>> > Is there a way to sort database results in a search command by = row? >>> > >>> > Thanksomuch, >>> > sfb >>> > >>> > >>> > >>> > >>> > >>> > >>> > Stephen F Braun >>> > sbraun1@twcny.rr.com = > >>> > --------------------------------------------------------- This >>> > message is sent to you because you are subscribed to the mailing >>> > list talk@webdna.us To unsubscribe, E-mail = to: >>> > talk-leave@webdna.us archives: >>> > http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: >>> > support@webdna.us >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list talk@webdna.us >>> To unsubscribe, E-mail to: talk-leave@webdna.us = >>> archives: http://www.webdna.us/page.dna?numero=3D55 = >>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us --Apple-Mail=_B0F4F810-DC17-4D84-8E1F-BD7ADFCE0B70 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
I was thinking the same thing.

Probably not a big help = or what you want to hear but I would consider reorganizing this data so = that it is properly normalized.

For example consider the following = field structure

SKU, DOW, SH, EH

1000,6,3,5

(Thats a day 6 block for 3 to 5pm)

This way you have essentiality the same = data and now you can group your results VERY easily buy Day of the week, = start times or endtimes.

While it feels like you have more data this way, you actually = have a ton less as in any standard DBS system you are blocking memory = for fields without or without data. And in the way you=E2=80=99re = dealing with now you not only are repeating verbose days over and over = (lots more text data), but also settings placeholder for ~40 fields = simply for 3 data elements.


If you really want to = do this right I would make the DOW a r_DOW field where the number = relates to a related sku in a day table so that you can easily adjust = spellings or dat abbreviations in Data and not in code.


HTH

AJ




On = Oct 18, 2017, at 4:59 AM, Stuart Tremain <webdna@idfk.com.au> = wrote:

Hi Stephen

A little bit vague on = what you are trying to achieve but:

You may have to do 7 searches, and then = sort the searches by hour for that day.

Search for all records =3D Monday = sorted by hours

There could be easier ways to achieve this depending on how = you have set up your db. If you have 40 fields in your db, why not give = them a position number i.e. 01 - 40 and then just sort by position = number ?





Kind regards

Stuart Tremain
Pharoah Lane = Software
AUSTRALIA
webdna@idfk.com.au






On 16 Oct 2017, at 15:29, Steve @ Tailored Web Solutions = <steve@tailoredwebsolutions.net> wrote:

I have an html form with 40ish checkboxes for hourly time = spans of each day, which correspond to fields in the database.
example:      FRIDAY_1_3= FRIDAY_11_1= FRIDAY_3_5= FRIDAY_9_11= MONDAY_1_3= MONDAY_11_1= MONDAY_3_5= MONDAY_9_11 etc...
The data = in the fields looks like this:   on= on= on= = on= on

The customer has asked me to sort the entire db by the days = of the week, then the hours of each day.
So I thought that = if I assigned a number value to each field:  3= 2= 4= 1= 7= 6= 8= 5
thought then I might be able to sort by these numbers, but I = didn't know how.

Thanks for asking,
sfb




Stephen Braun
Tailored Web Solutions
steve@tailoredwebsolutions.net
www.tailoredwebsolutions.com
315.343.1744

On Sun, Oct 15, 2017 at 10:58 = PM, Brian Fries <iphonzie@gmail.com> wrote:
Database sorting is always on = one or more columns, and effects the order of the rows returned.

Perhaps you could give = us an idea of the problem you are trying to solve, and we could be of = more help.

- = Brian

On Oct 15, 2017, at 7:50 PM, Steve @ Tailored = Web Solutions <steve@tailoredwebsolutions.net> wrote:

Yes, I can sort by one or more = (vertical) (column) fields

Is it possible to sort by (horizontal) rows?

Thanks,
sfb

Stephen Braun
Tailored Web Solutions
steve@tailoredwebsolutions.net
www.tailoredwebsolutions.com
315.343.1744

On Sun, Oct 15, 2017 at 7:12 = PM, Kenneth Grome <ken@webdnasolutions.com> wrote:
You can sort by one or = more fields.

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration


On 10/15/2017 11:41 AM, Stephen Braun wrote:
> Good Day All,
>
> Is there a way to sort  database results in a search command = by row?
>
> Thanksomuch,
> sfb
>
>
>
>
>
>
> Stephen F Braun
> sbraun1@twcny.rr.com <mailto:sbraun1@twcny.rr.com>
> --------------------------------------------------------- This
> message is sent to you because you are subscribed to the mailing
> list talk@webdna.us To unsubscribe, E-mail to:
> talk-leave@webdna.us archives:
> http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting:
> support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_B0F4F810-DC17-4D84-8E1F-BD7ADFCE0B70-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Sort by Row ("Steve @ Tailored Web Solutions" 2017)
  2. Re: [WebDNA] Sort by Row (Alex McCombie 2017)
  3. Re: [WebDNA] Sort by Row (Stuart Tremain 2017)
  4. Re: [WebDNA] Sort by Row (Brian Fries 2017)
  5. Re: [WebDNA] Sort by Row (Stuart Tremain 2017)
  6. Re: [WebDNA] Sort by Row (Kenneth Grome 2017)
  7. Re: [WebDNA] Sort by Row ("Steve @ Tailored Web Solutions" 2017)
  8. Re: [WebDNA] Sort by Row (Brian Fries 2017)
  9. Re: [WebDNA] Sort by Row ("Steve @ Tailored Web Solutions" 2017)
  10. Re: [WebDNA] Sort by Row (Kenneth Grome 2017)
  11. [WebDNA] Sort by Row (Stephen Braun 2017)
1285 --Apple-Mail=_B0F4F810-DC17-4D84-8E1F-BD7ADFCE0B70 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I was thinking the same thing. Probably not a big help or what you want to hear but I would consider = reorganizing this data so that it is properly normalized. For example consider the following field structure SKU, DOW, SH, EH 1000,6,3,5 (Thats a day 6 block for 3 to 5pm) This way you have essentiality the same data and now you can group your = results VERY easily buy Day of the week, start times or endtimes. While it feels like you have more data this way, you actually have a ton = less as in any standard DBS system you are blocking memory for fields = without or without data. And in the way you=E2=80=99re dealing with now = you not only are repeating verbose days over and over (lots more text = data), but also settings placeholder for ~40 fields simply for 3 data = elements. If you really want to do this right I would make the DOW a r_DOW field = where the number relates to a related sku in a day table so that you can = easily adjust spellings or dat abbreviations in Data and not in code. HTH AJ > On Oct 18, 2017, at 4:59 AM, Stuart Tremain = wrote: >=20 > Hi Stephen >=20 > A little bit vague on what you are trying to achieve but: >=20 > You may have to do 7 searches, and then sort the searches by hour for = that day. >=20 > Search for all records =3D Monday sorted by hours >=20 > There could be easier ways to achieve this depending on how you have = set up your db. If you have 40 fields in your db, why not give them a = position number i.e. 01 - 40 and then just sort by position number ? >=20 >=20 >=20 >=20 >=20 > Kind regards >=20 > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 >=20 >=20 >> On 16 Oct 2017, at 15:29, Steve @ Tailored Web Solutions = > = wrote: >>=20 >> I have an html form with 40ish checkboxes for hourly time spans of = each day, which correspond to fields in the database. >> example: FRIDAY_1_3FRIDAY_11_1= FRIDAY_3_5FRIDAY_9_11= MONDAY_1_3MONDAY_11_1= MONDAY_3_5MONDAY_9_11 etc... >> The data in the fields looks like this: onon= on= onon >>=20 >> The customer has asked me to sort the entire db by the days of the = week, then the hours of each day. >> So I thought that if I assigned a number value to each field: 3= 241= 768= 5 >> thought then I might be able to sort by these numbers, but I didn't = know how. >>=20 >> Thanks for asking, >> sfb >>=20 >>=20 >>=20 >>=20 >>=20 >> Stephen Braun >> Tailored Web Solutions >> steve@tailoredwebsolutions.net >> www.tailoredwebsolutions.com >> 315.343.1744 >>=20 >> On Sun, Oct 15, 2017 at 10:58 PM, Brian Fries > wrote: >> Database sorting is always on one or more columns, and effects the = order of the rows returned. >>=20 >> Perhaps you could give us an idea of the problem you are trying to = solve, and we could be of more help. >>=20 >> - Brian >>=20 >>> On Oct 15, 2017, at 7:50 PM, Steve @ Tailored Web Solutions = > = wrote: >>>=20 >>> Yes, I can sort by one or more (vertical) (column) fields >>>=20 >>> Is it possible to sort by (horizontal) rows? >>>=20 >>> Thanks, >>> sfb >>>=20 >>>=20 >>> Stephen Braun >>> Tailored Web Solutions >>> steve@tailoredwebsolutions.net = >>> www.tailoredwebsolutions.com >>> 315.343.1744 >>>=20 >>> On Sun, Oct 15, 2017 at 7:12 PM, Kenneth Grome = > wrote: >>> You can sort by one or more fields. >>>=20 >>> Regards, >>> Kenneth Grome >>> WebDNA Solutions >>> http://www.webdnasolutions.com >>> Web Database Systems and Linux Server Administration >>>=20 >>>=20 >>> On 10/15/2017 11:41 AM, Stephen Braun wrote: >>> > Good Day All, >>> > >>> > Is there a way to sort database results in a search command by = row? >>> > >>> > Thanksomuch, >>> > sfb >>> > >>> > >>> > >>> > >>> > >>> > >>> > Stephen F Braun >>> > sbraun1@twcny.rr.com = > >>> > --------------------------------------------------------- This >>> > message is sent to you because you are subscribed to the mailing >>> > list talk@webdna.us To unsubscribe, E-mail = to: >>> > talk-leave@webdna.us archives: >>> > http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: >>> > support@webdna.us >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list talk@webdna.us >>> To unsubscribe, E-mail to: talk-leave@webdna.us = >>> archives: http://www.webdna.us/page.dna?numero=3D55 = >>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us --Apple-Mail=_B0F4F810-DC17-4D84-8E1F-BD7ADFCE0B70 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
I was thinking the same thing.

Probably not a big help = or what you want to hear but I would consider reorganizing this data so = that it is properly normalized.

For example consider the following = field structure

SKU, DOW, SH, EH

1000,6,3,5

(Thats a day 6 block for 3 to 5pm)

This way you have essentiality the same = data and now you can group your results VERY easily buy Day of the week, = start times or endtimes.

While it feels like you have more data this way, you actually = have a ton less as in any standard DBS system you are blocking memory = for fields without or without data. And in the way you=E2=80=99re = dealing with now you not only are repeating verbose days over and over = (lots more text data), but also settings placeholder for ~40 fields = simply for 3 data elements.


If you really want to = do this right I would make the DOW a r_DOW field where the number = relates to a related sku in a day table so that you can easily adjust = spellings or dat abbreviations in Data and not in code.


HTH

AJ




On = Oct 18, 2017, at 4:59 AM, Stuart Tremain <webdna@idfk.com.au> = wrote:

Hi Stephen

A little bit vague on = what you are trying to achieve but:

You may have to do 7 searches, and then = sort the searches by hour for that day.

Search for all records =3D Monday = sorted by hours

There could be easier ways to achieve this depending on how = you have set up your db. If you have 40 fields in your db, why not give = them a position number i.e. 01 - 40 and then just sort by position = number ?





Kind regards

Stuart Tremain
Pharoah Lane = Software
AUSTRALIA
webdna@idfk.com.au






On 16 Oct 2017, at 15:29, Steve @ Tailored Web Solutions = <steve@tailoredwebsolutions.net> wrote:

I have an html form with 40ish checkboxes for hourly time = spans of each day, which correspond to fields in the database.
example:      FRIDAY_1_3= FRIDAY_11_1= FRIDAY_3_5= FRIDAY_9_11= MONDAY_1_3= MONDAY_11_1= MONDAY_3_5= MONDAY_9_11 etc...
The data = in the fields looks like this:   on= on= on= = on= on

The customer has asked me to sort the entire db by the days = of the week, then the hours of each day.
So I thought that = if I assigned a number value to each field:  3= 2= 4= 1= 7= 6= 8= 5
thought then I might be able to sort by these numbers, but I = didn't know how.

Thanks for asking,
sfb




Stephen Braun
Tailored Web Solutions
steve@tailoredwebsolutions.net
www.tailoredwebsolutions.com
315.343.1744

On Sun, Oct 15, 2017 at 10:58 = PM, Brian Fries <iphonzie@gmail.com> wrote:
Database sorting is always on = one or more columns, and effects the order of the rows returned.

Perhaps you could give = us an idea of the problem you are trying to solve, and we could be of = more help.

- = Brian

On Oct 15, 2017, at 7:50 PM, Steve @ Tailored = Web Solutions <steve@tailoredwebsolutions.net> wrote:

Yes, I can sort by one or more = (vertical) (column) fields

Is it possible to sort by (horizontal) rows?

Thanks,
sfb

Stephen Braun
Tailored Web Solutions
steve@tailoredwebsolutions.net
www.tailoredwebsolutions.com
315.343.1744

On Sun, Oct 15, 2017 at 7:12 = PM, Kenneth Grome <ken@webdnasolutions.com> wrote:
You can sort by one or = more fields.

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration


On 10/15/2017 11:41 AM, Stephen Braun wrote:
> Good Day All,
>
> Is there a way to sort  database results in a search command = by row?
>
> Thanksomuch,
> sfb
>
>
>
>
>
>
> Stephen F Braun
> sbraun1@twcny.rr.com <mailto:sbraun1@twcny.rr.com>
> --------------------------------------------------------- This
> message is sent to you because you are subscribed to the mailing
> list talk@webdna.us To unsubscribe, E-mail to:
> talk-leave@webdna.us archives:
> http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting:
> support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_B0F4F810-DC17-4D84-8E1F-BD7ADFCE0B70-- . Alex McCombie

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:

Kaaaaahhhhhhhnnnnnnn! (1997) Customer login feature (2004) Anyone here care to chime in? (2005) REPOST... Incompatibility with WebCat 3 templates ... (2000) RE: [WebDNA] webdna.us (2008) PLEASE REMOVE MY EMAIL ADDRESS (1997) [WebDNA] Encode cookies ONLY via "method=Base64" (2008) [WebDNA] online.db deadlock: your current options ... (2011) WC2.0 Memory Requirements (1997) WebDNA permissions? (2002) Version f1 status (1997) [url] (1997) [WebDNA] [OT] Free Windows FTP client recommendations (2009) Thanks Grant (1997) Max Record length (1997) Nesting format tags (1997) Password problems with WebCat 4.01 (2000) Online reference (1997) So many lookers, hey smith micro (2003) New Beta Documentation (1997)