[WebDNA] Searching for multiple bits of data in one field or use multiple

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113022
interpreted = N
texte = 610 --001a113ade82be9454053dae0781 Content-Type: text/plain; charset=UTF-8 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 --001a113ade82be9454053dae0781 Content-Type: text/html; charset=UTF-8 Content-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 to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a113ade82be9454053dae0781-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Searching for multiple bits of data in one field or use multiple fields for each bit of data? ("C. Frank Wofle" 2016)
  2. Re: [WebDNA] Searching for multiple bits of data in one field or use multiple fields for each bit of data? (Grant Hulbert 2016)
  3. 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)
  4. [WebDNA] Searching for multiple bits of data in one field or use multiple (dale 2016)
610 --001a113ade82be9454053dae0781 Content-Type: text/plain; charset=UTF-8 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 --001a113ade82be9454053dae0781 Content-Type: text/html; charset=UTF-8 Content-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 to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a113ade82be9454053dae0781-- . 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:

[WebDNA] setcookie then redirect (2013) Suggestion: appendfounditems (2002) More on the email templates (1997) Include vs. lookup? (1998) Verifying both name and password (was: THANKS) (1997) WebCatalog2 Feature Feedback (1996) group searching problem (2002) WebCat on Linux (2000) docs for WebCatalog2 (1997) [WebDNA] sort parameters in search (2015) ShipCosts database (1997) SiteGuard Use Question (1997) [off] Promotions/ECRC (1997) Referring URL (1998) multiple search commands (1997) Integration? (1999) WebCatalog for guestbook ? (1997) Cumulative Shipping charge calculations - your help please. (1997) emailer (1997) Question: Searching/Appending (1998)