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 = 113023
interpreted = N
texte = 611I think you should store each alarm condition as one bit in a binary =number long enough to accommodate all alarm conditions. Then, each base =10 value of that binary number represents a unique alarm or combination =of alarms.> On Sep 29, 2016, at 6:42 PM, dale
wrote:>=20> I searched the talk archives, though I probably didn't use the proper =search terms.>=20> 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.=20>=20> 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.=20>=20> 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.=20>=20> 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?>=20> I really haven't searched for multiple bits of data in a single field =before.=20>=20> 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>=20> 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.=20=>=20> Thank you in advance for any recommendations as to the best way to =handle this.=20>=20> Dale>=20> --------------------------------------------------------- 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 tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
611I think you should store each alarm condition as one bit in a binary =number long enough to accommodate all alarm conditions. Then, each base =10 value of that binary number represents a unique alarm or combination =of alarms.> On Sep 29, 2016, at 6:42 PM, dale wrote:>=20> I searched the talk archives, though I probably didn't use the proper =search terms.>=20> 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.=20>=20> 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.=20>=20> 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.=20>=20> 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?>=20> I really haven't searched for multiple bits of data in a single field =before.=20>=20> 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>=20> 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.=20=>=20> Thank you in advance for any recommendations as to the best way to =handle this.=20>=20> Dale>=20> --------------------------------------------------------- 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 tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Patrick McCormick
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:
Domain name & WebDNA 5.0 (2003)
[SHOWIF AND/OR] (1997)
problems with 2 tags shakur (1997)
Add a field to the error log? (1997)
includes and cart numbers (1997)
Single Link browsing (1997)
IP Shows Server (2003)
RE: Formulas.db + Users.db (1997)
WebCat for News Gathering (1999)
Updating Prices in Online Database (1999)
Bad Cookie (1998)
sendmail spaces (1997)
Cookies (1999)
lookups or math? (1998)
MasterCounter Weirdness -Resolved! (1997)
Extended [ConvertChars] (1997)
fieldType=num (1997)
Fun with Dates (syntax) (2002)
[WebDNA] Help with work-around format date (2013)
includes and cart numbers (1997)