Re: Data Entry ... Excel Style ... How To?

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 38563
interpreted = N
texte = I have done something similar.... Maybe this will help. Not sure about the limit on sending form data.1st page: return all the records in a form, save the value of [numfound] in a hidden field to pass to next page; save a unique record id (recNum) with the index info from the founditems in a hidden field. This is the page on which the user can edit any of the fields.
[search db=some.db&nerecNumdata=FIND_ALL] [founditems] [/founditems] [/search]
2nd page: After submit is a page that replaces all the records with whatever info is in the form fields. This is obviously not that efficient since I am actually replacing all the fields that are on the form as I can't tell which ones are changed. But it does work rather well.[loop start=1&end=[loopnum]] [replace db=some.db&eqrecNumdata=[interpret][recNum[index]][/interpret]]field1=[_fiel d1]& field2=[field2]&field3=[field3][/replace] [/loop]regards,Sally At 12:35 PM 9/11/01, you wrote: >Good day to all ... > >Objective : > >To extract data from a WCAT database, list it row by row in a table format >where each record has one or more fields (input boxes) with the extracted >data for change. The user, simply changes one or more records and when done, >click on one submit button to update all the changes made for records that >are affected (i.e. Records with no change remains as is). > >Question : > >Has any one done this or can any one propose or submit an example code >snippet for us to review .... That can achieve this Excel style of data >entry. > >As an example of how this code is to function ... Reference can be made to a >product catalog case. Say a product catalog has numerous fields per record >and one of those fields is PRICE. The end user wants to make a change to one >or many records on the PRICE field. > >This can be easily done by listing all records ... Then calling up each >record in turn ... To enter the PRICE change. However, what the end-user >wants is to call up all or list all records .... Then make the changes to >price across one or more of the displayed records and when done, clicking on >one submit button to change all the affected records. Basically ... It saves >time on having to call up each record independently to make the change. > >Found and Replace tag used in WCAT allows looping to change a field but with >one entry value .... Across many records. What is needed is something like >Found and Replace tag .... But able to replace different related values >across many records. > >Hope the explanation is sufficient to give you all an understanding of what >is desired. Any help on this would be much appreciated. I am certain there >is a work around or possible solution to this .... But me poor brain is >going soggy trying to figure out something .... Help if you can. > >Thanks again ... TDn > > >------------------------------------------------------------- >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://search.smithmicro.com/ > ------------------------------------------------------------- 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://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Data Entry ... Excel Style ... How To? (Andrew Simpson 2001)
  2. Re: Data Entry ... Excel Style ... How To? (Anup Setty 2001)
  3. Re: Data Entry ... Excel Style ... How To? (Sally Reidy 2001)
  4. Re: Data Entry ... Excel Style ... How To? (Andrew Simpson 2001)
  5. Re: Data Entry ... Excel Style ... How To? (Andrew Simpson 2001)
  6. Re: Data Entry ... Excel Style ... How To? (Aaron Lynch 2001)
  7. Data Entry ... Excel Style ... How To? (Terry Nair 2001)
I have done something similar.... Maybe this will help. Not sure about the limit on sending form data.1st page: return all the records in a form, save the value of [numfound] in a hidden field to pass to next page; save a unique record id (recNum) with the index info from the founditems in a hidden field. This is the page on which the user can edit any of the fields.
[search db=some.db&nerecNumdata=FIND_ALL] [founditems] [/founditems] [/search]
2nd page: After submit is a page that replaces all the records with whatever info is in the form fields. This is obviously not that efficient since I am actually replacing all the fields that are on the form as I can't tell which ones are changed. But it does work rather well.[loop start=1&end=[loopnum]] [replace db=some.db&eqrecNumdata=[interpret][recNum[index]][/interpret]]field1=[_fiel d1]& field2=[field2]&field3=[field3][/replace] [/loop]regards,Sally At 12:35 PM 9/11/01, you wrote: >Good day to all ... > >Objective : > >To extract data from a WCAT database, list it row by row in a table format >where each record has one or more fields (input boxes) with the extracted >data for change. The user, simply changes one or more records and when done, >click on one submit button to update all the changes made for records that >are affected (i.e. Records with no change remains as is). > >Question : > >Has any one done this or can any one propose or submit an example code >snippet for us to review .... That can achieve this Excel style of data >entry. > >As an example of how this code is to function ... Reference can be made to a >product catalog case. Say a product catalog has numerous fields per record >and one of those fields is PRICE. The end user wants to make a change to one >or many records on the PRICE field. > >This can be easily done by listing all records ... Then calling up each >record in turn ... To enter the PRICE change. However, what the end-user >wants is to call up all or list all records .... Then make the changes to >price across one or more of the displayed records and when done, clicking on >one submit button to change all the affected records. Basically ... It saves >time on having to call up each record independently to make the change. > >Found and Replace tag used in WCAT allows looping to change a field but with >one entry value .... Across many records. What is needed is something like >Found and Replace tag .... But able to replace different related values >across many records. > >Hope the explanation is sufficient to give you all an understanding of what >is desired. Any help on this would be much appreciated. I am certain there >is a work around or possible solution to this .... But me poor brain is >going soggy trying to figure out something .... Help if you can. > >Thanks again ... TDn > > >------------------------------------------------------------- >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://search.smithmicro.com/ > ------------------------------------------------------------- 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://search.smithmicro.com/ Sally Reidy

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:

accented chars. Please help me! (1998) A sendmail warning (2005) Summing fields (1997) FW: WebDNA-Talk searchable? (1997) multiple databases (1997) [capitalize] (2005) Multiple copies (1999) AOL (1999) Emailer (1998) [WebDNA] Not even sure what to ask for help on. . . :( (2008) DB Size - MAX (2004) Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997) formatting a number (1999) Updating Prices in Online Database (1999) SetLineItem (1997) 2nd WebCatalog2 Feature Request (1996) creating a ShipCosts database (1997) WC2.0 Memory Requirements (1997) Summing fields (1997) Ampersand (1997)