Re: Universal db access template ...

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 45068
interpreted = N
texte = >I fixed my copy Ken, I had this line wrapped from the email (I thought I had >corrected them all): > >[text]skuField=[listfields db=[thisDB]][showif >[index]=1][fieldname][/showif][/listfields][/text]Thanks for finding the problem Gary, I'm glad it's working for you now ... :) >This is a pretty neat little tool. I really like how you can easily sort >the data by any field with a number of different max= options.Yeah, I was using someone else's database access tool for a while, but I got sick of using their defaults for everything, and I didn't want to have to open the file and make manual changes all the time either. This tool set my own flexible values on the fly, and when I change them (at anytime) they keep their settings until I change them again or until I end the session -- which means no separate preference file to drag around and mess with all the time, and no manual code changes in the template. >Something that I've made (which would be a really easy implementation for >you I would think) would be to have a spreadsheet view. A view that would >mimic Excel so that you have the option of changing any number of fields >across a wide number of records all at once.Actually I did this in my first version of this tool ... and it was fine when I was also using text fields (instead of textarea fields) and finding a small number of records in db's with a small number of fields. But ... you cannot use text fields for updating db fields because the CR's which were input into textarea fields when the records are first created (and everything following the CR's in the same field) will be lost unless you use textarea fields in your update form -- thus the reason for all those two-line textarea fields.I also found that loading the page when the search context's max value was high, or when the db has many fields in it, was a slow process because of the time it takes the browser to render the page.Nevertheless, I may add this option to a future version some day (if I have the time to write the code) ... or if you or others feel like it, you can write it and submit your improved versions to the contest, or just post it online somewhere (such as Brian's web site) so people can use it for free ... :)>I really like your sorting features (columnar) and various max records >options.Yeah, me too, in fact these are the main reason why I built it. I would also like to add three more sorting options - for dates, times and numbers - and maybe multiple sorting options as well ... but I think these would have to be implemented in a search form in order to create the maximum functionality. And if a search form is used, then every possible search option could be offered, making this tool extremely useful -- not only for browsing as it is now, but also for true searching.But even as it is now, it still saves me a lot of time, especially when I'm developing a new db and need to check things as I go along -- without opening the db file in a text editor. Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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: Universal db access template ... (Kenneth Grome 2002)
  2. Re: Universal db access template ... (Kenneth Grome 2002)
  3. Re: Universal db access template ... (Kenneth Grome 2002)
  4. Re: Universal db access template ... (Alain Russell 2002)
  5. Re: Universal db access template ... (Alain Russell 2002)
  6. Re: Universal db access template ... (Gary Krockover 2002)
  7. Re: Universal db access template ... (Joe D'Andrea 2002)
  8. Re: Universal db access template ... (Gary Krockover 2002)
  9. Re: Universal db access template ... (Kenneth Grome 2002)
  10. Re: Universal db access template ... (Gary Krockover 2002)
  11. Re: Universal db access template ... (Kenneth Grome 2002)
  12. Universal db access template ... (Kenneth Grome 2002)
>I fixed my copy Ken, I had this line wrapped from the email (I thought I had >corrected them all): > >[text]skuField=[listfields db=[thisDB]][showif >[index]=1][fieldname][/showif][/listfields][/text]Thanks for finding the problem Gary, I'm glad it's working for you now ... :) >This is a pretty neat little tool. I really like how you can easily sort >the data by any field with a number of different max= options.Yeah, I was using someone else's database access tool for a while, but I got sick of using their defaults for everything, and I didn't want to have to open the file and make manual changes all the time either. This tool set my own flexible values on the fly, and when I change them (at anytime) they keep their settings until I change them again or until I end the session -- which means no separate preference file to drag around and mess with all the time, and no manual code changes in the template. >Something that I've made (which would be a really easy implementation for >you I would think) would be to have a spreadsheet view. A view that would >mimic Excel so that you have the option of changing any number of fields >across a wide number of records all at once.Actually I did this in my first version of this tool ... and it was fine when I was also using text fields (instead of textarea fields) and finding a small number of records in db's with a small number of fields. But ... you cannot use text fields for updating db fields because the CR's which were input into textarea fields when the records are first created (and everything following the CR's in the same field) will be lost unless you use textarea fields in your update form -- thus the reason for all those two-line textarea fields.I also found that loading the page when the search context's max value was high, or when the db has many fields in it, was a slow process because of the time it takes the browser to render the page.Nevertheless, I may add this option to a future version some day (if I have the time to write the code) ... or if you or others feel like it, you can write it and submit your improved versions to the contest, or just post it online somewhere (such as Brian's web site) so people can use it for free ... :)>I really like your sorting features (columnar) and various max records >options.Yeah, me too, in fact these are the main reason why I built it. I would also like to add three more sorting options - for dates, times and numbers - and maybe multiple sorting options as well ... but I think these would have to be implemented in a search form in order to create the maximum functionality. And if a search form is used, then every possible search option could be offered, making this tool extremely useful -- not only for browsing as it is now, but also for true searching.But even as it is now, it still saves me a lot of time, especially when I'm developing a new db and need to check things as I go along -- without opening the db file in a text editor. Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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/ 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:

[WebDNA] Re-sending email (2018) WebCatalog2 Feature Feedback (1996) [WebDNA] TCPconnect and Bitcoin rate (2019) Modifying Carts (1999) Shopping Cart Directory (2000) James Hawker (1998) Moving Files (2000) [WebDNA] WebDNA & Mod_rewrite (2010) WebCat2b13 Command Reference Doc error (1997) security (1997) WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997) Re:2nd WebCatalog2 Feature Request (1996) Document Contains No Data! (1997) Convert Chars Q (2000) Big Databases (1997) Webcatalog, Webstar and Crasharama (1999) Exclude by date - multiple (1997) Deleting with contexts (2001) send mail problem? (1997) Showif, Hideif reverse logic ? (1997)