Re: Cart Number sequence

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14055
interpreted = N
texte = >I assume that a cart number assigned at 10:00am today is lower in number >then one assigned at 10:05am today. So one can sort on the cart number and >get the newest one at the top.You can sort the cart numbers if you want to, but do *NOT* tell WebCat that the cart number is a NUMBER. In other words, don't put &fieldtype=num into your search string when the field has values that were generated by the [cart] function, because in reality the cart numbers don't have the same number of digits all the time - sometimes they have 12 digits, sometimes 13, sometimes 14.That's not important unless you're sorting cart numbers, and then you have to sort them as if they are text values instead of numbers, that's all.>Would there ever be a time that the cart >number would roll over and be a lower number. IE if cartnumber is greater >then 999 then cartnumber=1Yes, but there is no 'roll-over'. The only time you may *possibly* get repetitive cart numbers is when you reset your server's clock to an earlier time. That's because the cart number is created by using the time and date, and if you reset the clock to an *earlier* time, then it's possible (but still not very likely) that a new cart number will be created that has the same value as a previous cart number.Sincerely, Ken Grome WebDNA Solutions 808-737-6499 Associated Messages, from the most recent to the oldest:

    
  1. Re: Cart Number sequence (Kenneth Grome 1997)
  2. Re: Cart Number sequence (grichter@panavise.com (Gary Richter) 1997)
  3. Re: Cart Number sequence (Grant Hulbert 1997)
  4. Cart Number sequence (grichter@panavise.com (Gary Richter) 1997)
>I assume that a cart number assigned at 10:00am today is lower in number >then one assigned at 10:05am today. So one can sort on the cart number and >get the newest one at the top.You can sort the cart numbers if you want to, but do *NOT* tell WebCat that the cart number is a NUMBER. In other words, don't put &fieldtype=num into your search string when the field has values that were generated by the [cart] function, because in reality the cart numbers don't have the same number of digits all the time - sometimes they have 12 digits, sometimes 13, sometimes 14.That's not important unless you're sorting cart numbers, and then you have to sort them as if they are text values instead of numbers, that's all.>Would there ever be a time that the cart >number would roll over and be a lower number. IE if cartnumber is greater >then 999 then cartnumber=1Yes, but there is no 'roll-over'. The only time you may *possibly* get repetitive cart numbers is when you reset your server's clock to an earlier time. That's because the cart number is created by using the time and date, and if you reset the clock to an *earlier* time, then it's possible (but still not very likely) that a new cart number will be created that has the same value as a previous cart number.Sincerely, Ken Grome WebDNA Solutions 808-737-6499 Kenneth Grome

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:

Help formatting search results w/ table (1997) Trouble with formula.db + more explanation (1997) Lost and Recovered. (1998) [WriteFile] problems (1997) Calculating Shipping (1997) Indexing Web sites? (2000) Setting up WebCatalog with Retail Pro data (1996) protect tag on NT IIS (1997) Version f1 status (1997) Showing specific [cart] contents (1998) (2004) [WriteFile] problems (1997) TeaRoom Order fields email account remain empty even though thewy are filled. (1997) Locking up with WebCatalog... (1997) wish list (2002) Help! (2000) HEADER AND FOOTER (1997) Grouping Fields in Context (1999) Permissions (2000) Convert Chars Q (2000)