texte = 610--001a113ade82be9454053dae0781Content-Type: text/plain; charset=UTF-8I searched the talk archives, though I probably didn't use the propersearch terms.The system for work I will be building is kind of like a fleet managementsystem. It isn't tracking the vehicles, but a computer and camera system weinstall 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 itwould be easier to search for systems that had a specific problem and/orcombination of problems.As it has been a few years since coding in WebDNA, I'm not sure if this isthe best way or not. We do come up with new codes as time passes based onnew systems.Would you recommend using a single field for various codes as listed abovewhere I would only have to change the searches or using a hdr file to makeadding additional codes a bit easier?I really haven't searched for multiple bits of data in a single fieldbefore.Ways in which this would be used:Someone checking the systems remotely would enter the code for that systemTechs fixing the system would need to remove the appropriate codes for whatthey fixedRunning reports to determine which systems have certain issuesAdditionally, 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 notesin a history database so we will have a life-cycle of the system. Thoserecords would only be editable by certain admin accounts.Thank you in advance for any recommendations as to the best way to handlethis.Dale--001a113ade82be9454053dae0781Content-Type: text/html; charset=UTF-8Content-Transfer-Encoding: quoted-printable
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 tracki=ng the vehicles, but a computer and camera system we install and maintain o=n the vehicles.=C2=A0
One of the things I wanted t=o do is to put the various problem codes (e.g. C HD PCB SSD) in a single fi=eld separated by a comma. My thought is that it would be easier to search f=or systems that had a specific problem and/or combination of problems.=C2==A0
As it has been a few years since coding in Web=DNA, I'm not sure if this is the best way or not. We do come up with ne=w codes as time passes based on new systems.=C2=A0
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 ha=ven't searched for multiple bits of data in a single field before.=C2==A0
Ways in which this would be used:
So=meone 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 ha=ve certain issues
Additionally, each time the tech=s create a service ticket to make a repair, I will save a copy of the the s=tatus 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 c=ertain admin accounts.=C2=A0
Thank you in advance =for any recommendations as to the best way to handle this.=C2=A0
=
Dale
---------------------------------------------------------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--001a113ade82be9454053dae0781--.
Associated Messages, from the most recent to the oldest:
610--001a113ade82be9454053dae0781Content-Type: text/plain; charset=UTF-8I searched the talk archives, though I probably didn't use the propersearch terms.The system for work I will be building is kind of like a fleet managementsystem. It isn't tracking the vehicles, but a computer and camera system weinstall 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 itwould be easier to search for systems that had a specific problem and/orcombination of problems.As it has been a few years since coding in WebDNA, I'm not sure if this isthe best way or not. We do come up with new codes as time passes based onnew systems.Would you recommend using a single field for various codes as listed abovewhere I would only have to change the searches or using a hdr file to makeadding additional codes a bit easier?I really haven't searched for multiple bits of data in a single fieldbefore.Ways in which this would be used:Someone checking the systems remotely would enter the code for that systemTechs fixing the system would need to remove the appropriate codes for whatthey fixedRunning reports to determine which systems have certain issuesAdditionally, 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 notesin a history database so we will have a life-cycle of the system. Thoserecords would only be editable by certain admin accounts.Thank you in advance for any recommendations as to the best way to handlethis.Dale--001a113ade82be9454053dae0781Content-Type: text/html; charset=UTF-8Content-Transfer-Encoding: quoted-printable