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 = 113024
interpreted = N
texte = 612 --001a113de59a505b44053dbcdbfd Content-Type: text/plain; charset=UTF-8 Hello Patrick, Interesting idea. I've not tried that in the past. Any possible examples of how you would do that? It definitely sounds like a good way to go. Thank you, Dale On Fri, Sep 30, 2016 at 10:06 AM, Patrick McCormick < duganmccormick@gmail.com> wrote: > I 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: > > > > 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 > --001a113de59a505b44053dbcdbfd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Patrick,

Interesting idea. I'= ve not tried that in the past. Any possible examples of how you would do th= at? It definitely sounds like a good way to go.

Th= ank you,

Dale

On Fri, Sep 30, 2016 at 10:06 AM, Patrick = McCormick <duganmccormick@gmail.com> wrote:
I think you should store each alarm condition as o= ne bit in a binary number long enough to accommodate all alarm conditions.= =C2=A0 Then, each base 10 value of that binary number represents a unique a= larm or combination of alarms.


> On Sep 29, 2016, at 6:42 PM, dale <dtherio@gmail.com> wrote:
>
> I searched the talk archives, though I probably didn't use the pro= per search terms.
>
> The system for work I will be building is kind of like a fleet managem= ent system. It isn't tracking the vehicles, but a computer and camera s= ystem 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 th= at 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 b= ased on new systems.
>
> Would you recommend using a single field for various codes as listed a= bove 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 fi= eld before.
>
> Ways in which this would be used:
> Someone checking the systems remotely would enter the code for that sy= stem
> 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 re= pair, I will save a copy of the the status of the system along with their n= otes in a history database so we will have a life-cycle of the system. Thos= e records would only be editable by certain admin accounts.
>
> Thank you in advance for any recommendations as to the best way to han= dle this.
>
> Dale
>
> -----------------------------------------------------= ---- This message is sent to you because you are subscribed to the mailing = list . To unsubscribe, E-mail to: archives: http://mail.web= dna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
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 --001a113de59a505b44053dbcdbfd-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Searching for multiple bits of data in one field or use (Patrick McCormick 2016)
  2. Re: [WebDNA] Searching for multiple bits of data in one field or use multiple fields for each bit of data? ("C. Frank Wofle" 2016)
  3. Re: [WebDNA] Searching for multiple bits of data in one field or use multiple fields for each bit of data? (Grant Hulbert 2016)
  4. Re: [WebDNA] Searching for multiple bits of data in one field or use (Kenneth Grome 2016)
  5. Re: [WebDNA] Searching for multiple bits of data in one field or use (dale 2016)
  6. Re: [WebDNA] Searching for multiple bits of data in one field or use (Patrick McCormick 2016)
  7. Re: [WebDNA] Searching for multiple bits of data in one field or use multiple fields for each bit of data? (christophe.billiottet@webdna.us 2016)
  8. Re: [WebDNA] Searching for multiple bits of data in one field or use (Patrick McCormick 2016)
  9. Re: [WebDNA] Searching for multiple bits of data in one field or use (dale 2016)
  10. Re: [WebDNA] Searching for multiple bits of data in one field or use (Patrick McCormick 2016)
  11. [WebDNA] Searching for multiple bits of data in one field or use multiple (dale 2016)
612 --001a113de59a505b44053dbcdbfd Content-Type: text/plain; charset=UTF-8 Hello Patrick, Interesting idea. I've not tried that in the past. Any possible examples of how you would do that? It definitely sounds like a good way to go. Thank you, Dale On Fri, Sep 30, 2016 at 10:06 AM, Patrick McCormick < duganmccormick@gmail.com> wrote: > I 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: > > > > 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 > --001a113de59a505b44053dbcdbfd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Patrick,

Interesting idea. I'= ve not tried that in the past. Any possible examples of how you would do th= at? It definitely sounds like a good way to go.

Th= ank you,

Dale

On Fri, Sep 30, 2016 at 10:06 AM, Patrick = McCormick <duganmccormick@gmail.com> wrote:
I think you should store each alarm condition as o= ne bit in a binary number long enough to accommodate all alarm conditions.= =C2=A0 Then, each base 10 value of that binary number represents a unique a= larm or combination of alarms.


> On Sep 29, 2016, at 6:42 PM, dale <dtherio@gmail.com> wrote:
>
> I searched the talk archives, though I probably didn't use the pro= per search terms.
>
> The system for work I will be building is kind of like a fleet managem= ent system. It isn't tracking the vehicles, but a computer and camera s= ystem 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 th= at 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 b= ased on new systems.
>
> Would you recommend using a single field for various codes as listed a= bove 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 fi= eld before.
>
> Ways in which this would be used:
> Someone checking the systems remotely would enter the code for that sy= stem
> 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 re= pair, I will save a copy of the the status of the system along with their n= otes in a history database so we will have a life-cycle of the system. Thos= e records would only be editable by certain admin accounts.
>
> Thank you in advance for any recommendations as to the best way to han= dle this.
>
> Dale
>
> -----------------------------------------------------= ---- This message is sent to you because you are subscribed to the mailing = list . To unsubscribe, E-mail to: archives: http://mail.web= dna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
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 --001a113de59a505b44053dbcdbfd-- . dale

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:

Signal Raised (1997) Slow applescript context ... (2000) AAgghh!! Help, please. SSL strikes again. (1997) Running 2 two WebCatalog.acgi's (1996) The beginning (1997) Trouble with formula.db (1997) More questions about serial number dishing (1997) Problems with SELECT MULTIPLE (1999) Authenticate (1997) Stopping bad HTML propagation ? (1997) How to Display text in empty fields (1997) Limiting user access to .tmpl files (1997) Searchable list archive (1997) Where's Cart Created ? (1997) US Postal Service API (2007) if else problem (2003) encryption madness (2003) Extract my page name (2006) Separate SSL Server (1997) carriage returns in data (1997)