Re: [WebDNA] Searching for multiple bits of data in one field or use
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113031
interpreted = N
texte = 619 I would just do it your way, assuming none of the problem codes have commas in them. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration On 09/29/2016 06:42 PM, dale wrote: > I searched the talk archives, though I probably didn't use the > proper search terms. > > The system for work I will be building is kind of like a fleet > management system. It isn't tracking the vehicles, but a computer > and camera system we install and maintain on the vehicles. > > One of the things I wanted to do is to put the various problem > codes (e.g. C HD PCB SSD) in a single field separated by a comma. > My thought is that it would be easier to search for systems that > had a specific problem and/or combination of problems. > > As it has been a few years since coding in WebDNA, I'm not sure if > this is the best way or not. We do come up with new codes as time > passes based on new systems. > > Would you recommend using a single field for various codes as > listed above where I would only have to change the searches or > using a hdr file to make adding additional codes a bit easier? > > I really haven't searched for multiple bits of data in a single > field before. > > Ways in which this would be used: > Someone checking the systems remotely would enter the code for > that system > Techs fixing the system would need to remove the appropriate codes > for what they fixed > Running reports to determine which systems have certain issues > > Additionally, each time the techs create a service ticket to make > a repair, I will save a copy of the the status of the system along > with their notes in a history database so we will have a > life-cycle of the system. Those records would only be editable by > certain admin accounts. > > Thank you in advance for any recommendations as to the best way to > handle this. > > Dale > > --------------------------------------------------------- This > message is sent to you because you are subscribed to the mailing > list . To unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
619 I would just do it your way, assuming none of the problem codes have commas in them. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration On 09/29/2016 06:42 PM, dale wrote: > I searched the talk archives, though I probably didn't use the > proper search terms. > > The system for work I will be building is kind of like a fleet > management system. It isn't tracking the vehicles, but a computer > and camera system we install and maintain on the vehicles. > > One of the things I wanted to do is to put the various problem > codes (e.g. C HD PCB SSD) in a single field separated by a comma. > My thought is that it would be easier to search for systems that > had a specific problem and/or combination of problems. > > As it has been a few years since coding in WebDNA, I'm not sure if > this is the best way or not. We do come up with new codes as time > passes based on new systems. > > Would you recommend using a single field for various codes as > listed above where I would only have to change the searches or > using a hdr file to make adding additional codes a bit easier? > > I really haven't searched for multiple bits of data in a single > field before. > > Ways in which this would be used: > Someone checking the systems remotely would enter the code for > that system > Techs fixing the system would need to remove the appropriate codes > for what they fixed > Running reports to determine which systems have certain issues > > Additionally, each time the techs create a service ticket to make > a repair, I will save a copy of the the status of the system along > with their notes in a history database so we will have a > life-cycle of the system. Those records would only be editable by > certain admin accounts. > > Thank you in advance for any recommendations as to the best way to > handle this. > > Dale > > --------------------------------------------------------- This > message is sent to you because you are subscribed to the mailing > list . To unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
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 name our technology! (1997)
Credit Card Checksum (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Nested tags count question (1997)
form validator issue (2005)
SERIAL NUMBER BEING LOST AGAIN!!! (1999)
WebCatalog for guestbook ? (1997)
Mozilla/4. and Browser Info.txt (1997)
[shell] command (2000)
Explorer 3.0 (1997)
Site Builder & IE Mac (2004)
Performance of this mailserver (2000)
WebCat Emailer & Liststar (1997)
WebDNA 4.5.1 Now Available (2003)
RE: WebCat cannot handle compatible search parameters? (1997)
Fun with dates (1997)
Mac: LModelDirector bug fix (1997)
Process SSI and WebCatalog.acgi (1998)
date (1999)
[WebDNA] Request to specify the sendmail file name (2015)