Thank you Chris and Patrick,
Sounds lik= e the way to go.
Basically I work on the stoparm c= amera systems on school buses. Currently we use various excel sheets and ma= nually filled out pdf forms. We could have codes that a camera is out, bad = data drive, bad OS drive, computer unit needs replacing, bad modem, gps puc= k, etc. We use 1-3 char codes for each issue. As we roll out newer systems = there can be different codes.
I could also use you= r suggestion to not which camera is out as well. I can have a green square/= dot for good and a red square/dot for bad.=C2=A0
T= hank you again, very cool!
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 --001a113506bed212d6053dbe0bd0-- .
Associated Messages, from the most recent to the oldest:
616 --001a113506bed212d6053dbe0bd0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you Chris and Patrick, Sounds like the way to go. Basically I work on the stoparm camera systems on school buses. Currently we use various excel sheets and manually filled out pdf forms. We could have codes that a camera is out, bad data drive, bad OS drive, computer unit needs replacing, bad modem, gps puck, etc. We use 1-3 char codes for each issue. As we roll out newer systems there can be different codes. I could also use your suggestion to not which camera is out as well. I can have a green square/dot for good and a red square/dot for bad. Thank you again, very cool! Dale On Fri, Sep 30, 2016 at 12:55 PM, Patrick McCormick < duganmccormick@gmail.com> wrote: > It=E2=80=99s elegant, compact and intuitive. None of which is possible wi= th PHP! > > > > On Sep 30, 2016, at 12:53 PM, christophe.billiottet@webdna.us wrote: > > > > I did something like that once. > > > > A database field had to store the type of invitation we had to send to > the customer > > > > it was something like an agenda: cocktail-press-exhibition- > embassy-catalog-museum-wife=E2=80=A6 > > > > Each customer could belong to several categories. > > > > > > In one field, I stored data like 00101100=E2=80=A6 > > > > [showif [GetChars start=3D2&end=3D2][agenda][/GetChars]=3D1] etc=E2=80= =A6 > > > > you get the idea. > > > > - chris > > > > > > > >> On Sep 30, 2016, at 20:23, dale wrote: > >> > >> 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 t= o > 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 fo= r > 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 the= ir > 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 > --001a113506bed212d6053dbe0bd0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable