Re: [table] strange behaviour REAL solution

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 49933
interpreted = N
texte = At 1:22 PM 5/1/03, Tim Robinson wrote: >Of course, this still doesn't explain why it only happens when the sort is >on the PRICE field and not the sku field....Because you have empty records in your database. WebDNA does not require a CR after a [founditems] in order for the records to display properly. In fact you can test this by removing your entire [founditems] context.If you just do [search ...][numfound][/search] you will see that the number of items returned depends on your search criteria and has nothing to do with what is or isn't in your [founditmes] context or whether there even is or isn't a [founditems] context.This is from a previous post of your's: At 12:43 PM 5/1/03, Tim Robinson wrote: >The $ didn't make any difference. So I tried the only thing that's >different between yours and mine: i changed neskudata=find_all to >neskudata=[blank]... and... it worked.Of course it worked. In the first search you're finding all records. That's why you get 24 records and why the html table appears to display improperly. But the html table is not displaying improperly... you're seeing blank records.When you change the search parameter in your second try above, you are saying find all records where the SKU is not equal to [blank] .... which is the same as saying find all records that are NOT empty in the SKU field. You get 12 records and the html table appears (and is) as expected.Your problem is that you have blank records in your database most likely the result of an incorrect line ending characters for your operating system(s).Good luck.~joe-- ____________________________________________________________ Joseph D'Andrea ~ http://www.west21.com/ ~ JoeDan@West21.com WEST21.com Internet services for the 21st Century webhosting ~ co-location ~ wireless access WebCat and MGI database programming ____________________________________________________________------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: [table] strange behaviour REAL solution (Joe D'Andrea 2003)
  2. Re: [table] strange behaviour REAL solution (Tim Robinson 2003)
  3. Re: [table] strange behaviour REAL solution (dbrooke 2003)
  4. Re: [table] strange behaviour REAL solution (Joe D'Andrea 2003)
  5. Re: [table] strange behaviour REAL solution (Tim Robinson 2003)
  6. Re: [table] strange behaviour REAL solution (WJ Starck 2003)
  7. Re: [table] strange behaviour REAL solution (Tim Robinson 2003)
At 1:22 PM 5/1/03, Tim Robinson wrote: >Of course, this still doesn't explain why it only happens when the sort is >on the PRICE field and not the sku field....Because you have empty records in your database. WebDNA does not require a CR after a [founditems] in order for the records to display properly. In fact you can test this by removing your entire [founditems] context.If you just do [search ...][numfound][/search] you will see that the number of items returned depends on your search criteria and has nothing to do with what is or isn't in your [founditmes] context or whether there even is or isn't a [founditems] context.This is from a previous post of your's: At 12:43 PM 5/1/03, Tim Robinson wrote: >The $ didn't make any difference. So I tried the only thing that's >different between yours and mine: i changed neskudata=find_all to >neskudata=[blank]... and... it worked.Of course it worked. In the first search you're finding all records. That's why you get 24 records and why the html table appears to display improperly. But the html table is not displaying improperly... you're seeing blank records.When you change the search parameter in your second try above, you are saying find all records where the SKU is not equal to [blank] .... which is the same as saying find all records that are NOT empty in the SKU field. You get 12 records and the html table appears (and is) as expected.Your problem is that you have blank records in your database most likely the result of an incorrect line ending characters for your operating system(s).Good luck.~joe-- ____________________________________________________________ Joseph D'Andrea ~ http://www.west21.com/ ~ JoeDan@West21.com WEST21.com Internet services for the 21st Century webhosting ~ co-location ~ wireless access WebCat and MGI database programming ____________________________________________________________------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Joe D'Andrea

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:

RAM variables (1997) Bug Report, maybe (1997) user/password validation (1998) [WriteFile] problems (1997) select multiple 2 more cents (1997) charge.com (2005) WCS Newbie question (1997) Database Strategy - more... (1998) emailer settings and control questions (1997) Database Updates (1997) For those of you not on the WebCatalog Beta... (1997) emailer (1997) could someone please try this - it's very quick and easy (2000) PCS Frames (1997) InternetWeek E-Commerce article (1998) carriage returns in data (1997) WebCatalog2 Feature Feedback (1996) Reserved words - Enhancement request (2000) Re:Can anyone help me with this shipping thing? (1998) Hard Questions ? (1997)