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 <dtherio@gmail.com> 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 <talk@webdna.us>.
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
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 <dtherio@gmail.com> 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 <talk@webdna.us>.
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
DOWNLOAD WEBDNA NOW!
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...