Knowledge Base Application

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am attempting to design a troubleshooting guide for my company with Acess
2k. I am currently building separate tables for each topic such as PRL
Update, No Signal, etc. I have separate fields for questions and answers. I
know it is a daunting and ambitious task for a newbie, but I want to try.
Are there any resources available to get me started? I have the info posted
regading Normalization. Now I need a sample template to model after. I
appreciate your help in advance.
 
Thanks for the quick response. Actually, I have one of these too from the
same site. From here, I want to start building the form. Let me elaborate:

The user clicks a combo box to access troubleshooting issues, and chooses
one. Then the first suggestion comes up "Is the feature on the account?" The
user can check "Yes" or "No". After checking, another suggestion comes up
based on the appropriate check...until all suggestions are exhausted.

Once I finish reading and making sure my data is set up properly, I want to
jump into the next step of creating the form that will run the app.

I will mention that code is like hieroglyphics to me right now. I've been
able to decipher a few things to finish a previous simple app, but i'm
stepping up the game now.

Any further help will be Gold.
 
I am attempting to design a troubleshooting guide for my company with Acess
2k. I am currently building separate tables for each topic such as PRL
Update, No Signal, etc. I have separate fields for questions and answers. I
know it is a daunting and ambitious task for a newbie, but I want to try.
Are there any resources available to get me started? I have the info posted
regading Normalization. Now I need a sample template to model after. I
appreciate your help in advance.
Click to expand...

Storing DATA - such as the type of problem - in a tablename is *not* a
good idea. And storing questions in fieldnames (as I gather you're
doing) is even worse - if you have to add or change a question, you
need to redesign your table, and all queries, forms, and reports
involving that table!

You might want to look at a top-notch questionnaire database; it's a
bit different in that it's designed for surveys, but it will capture
the correct approach to handle multiple questions and answers on
multiple subjects:

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='At Your Survey 2000'


John W. Vinson[MVP]
 
Thanks John,

Well, I hope that I'm being as clear as possible, but I may not be. I am
building a table for each topic: tblPRL, tblNoSignal, tblAuthentication,
tblCallerID, tblUnableToMakeCalls, etc. Under each table, I have field
names: "questions", "suggestions" and list suggestions and questions under
the respective field names.

So, with that said, I feel like I am building the tables correctly, now i
need to figure out how to set up the form. I will check out the questionnare
you referred, but any additional help would be again, gold.
 
Why not include a field for the Topic (PRL, Signal, Authentication, etc) and
maybe an extra field for a comment or explaination? Then you have one table
that stores the data. This in turn makes the form much easier, since
otherwise you'd probably have to build a form per table.
 
Thanks John,

Well, I hope that I'm being as clear as possible, but I may not be. I am
building a table for each topic: tblPRL, tblNoSignal, tblAuthentication,
tblCallerID, tblUnableToMakeCalls, etc. Under each table, I have field
names: "questions", "suggestions" and list suggestions and questions under
the respective field names.

So, with that said, I feel like I am building the tables correctly, now i
need to figure out how to set up the form. I will check out the questionnare
you referred, but any additional help would be again, gold.
Click to expand...

I'm sorry... but no, you are NOT building the tables correctly.

Data should be stored *IN FIELDS IN THE TABLES*. You're storing data -
the identity of a problem - in the table name; you're storing data -
questions - in field names.

If you have many problems to consider, you should have a table of
Problems with a ProblemID and a ProblemName; the Problem Name might be
"No Signal", "Authentication", etc.

If each problem involves many questions, you should have a second
table, Questions, with fields for ProblemID (as a link to the table of
Problems), QuestionNo, and the text of the question. Similarly for
Suggestions.

Perhaps I'm misunderstanding; if I am, please post the names and
fieldnames of your tables (or some typical tables), with examples of
the data that they contain.

John W. Vinson[MVP]
 
John, I see now why you get paid the BIG BUCKS!!!

Looking at your answer and the Survey Database, I have reformatted the
tables to look like this:

tblProblems
ProblemID ProblemName
PRL PRL228
NSG No Signal
AUT Authentication


tblQuestions
ProblemID QuestionNo QuestionName
PRL PRL01 Is there coverage?
NSG NSG01 Is there power to device?
AUT AUT01 Is the right feature added to account?


tblSuggestions
ProblemID SuggestionID SuggestionName?
PRL PRLS01 Make sure device is updated.
NSG NSGS02 Reprogram device.
AUT AUTS03 Call telesales.

Please tell me I interpreted this correctly, because I feel good about this,
and it definately makes more sense with my data. Even though I'm not
entering any new "per call" information, it allows me to add or remove any
new suggestions or questions. This is just first tier, so the tshooting is
not extensive. Am I ready to begin with the form now??? <g> (Thank you so
much)
 
John, I see now why you get paid the BIG BUCKS!!!
Click to expand...

Don't I wish... said:
Looking at your answer and the Survey Database, I have reformatted the
tables to look like this:

tblProblems
ProblemID ProblemName
PRL PRL228
NSG No Signal
AUT Authentication


tblQuestions
ProblemID QuestionNo QuestionName
PRL PRL01 Is there coverage?
NSG NSG01 Is there power to device?
AUT AUT01 Is the right feature added to account?
Click to expand...

Just note that you might have many rows all with ProblemID "NSG" - all
the different questions that might be asked to deal with a no-signal
condition. Note also that it's probably not necessary to include the
text string "NSG" in the QuestionNo field; you can instead just use an
Integer number field, and values 1, 2, 3 and so on. If you wish to see
the problem and question number together on screen, you can just
concatenate them:

[ProblemID] & Format([QuestionNo], "00")
tblSuggestions
ProblemID SuggestionID SuggestionName?
PRL PRLS01 Make sure device is updated.
NSG NSGS02 Reprogram device.
AUT AUTS03 Call telesales.
Click to expand...

Well... this makes sense if Suggestions and Questions are completely
independent. If a Suggestion applies to a particular Question, then
you should link to tblQuestions, probably by the two fields ProblemID
and QuestionNo.

This would let you deal with the question "Is there power to device?"
by providing an answer "Maybe it would work better if you plugged it
in" - which might not be an appropriate suggestion in other contexts.
Please tell me I interpreted this correctly, because I feel good about this,
and it definately makes more sense with my data. Even though I'm not
entering any new "per call" information, it allows me to add or remove any
new suggestions or questions. This is just first tier, so the tshooting is
not extensive. Am I ready to begin with the form now??? <g> (Thank you so
Click to expand...

You're getting a lot closer.

John W. Vinson[MVP]
 
John Vinson said:
John, I see now why you get paid the BIG BUCKS!!!
Click to expand...

Don't I wish... said:
Looking at your answer and the Survey Database, I have reformatted the
tables to look like this:

tblProblems
ProblemID ProblemName
PRL PRL228
NSG No Signal
AUT Authentication


tblQuestions
ProblemID QuestionNo QuestionName
PRL PRL01 Is there coverage?
NSG NSG01 Is there power to device?
AUT AUT01 Is the right feature added to account?
Click to expand...

Just note that you might have many rows all with ProblemID "NSG" - all
the different questions that might be asked to deal with a no-signal
condition. Note also that it's probably not necessary to include the
text string "NSG" in the QuestionNo field; you can instead just use an
Integer number field, and values 1, 2, 3 and so on. If you wish to see
the problem and question number together on screen, you can just
concatenate them:

[ProblemID] & Format([QuestionNo], "00")
tblSuggestions
ProblemID SuggestionID SuggestionName?
PRL PRLS01 Make sure device is updated.
NSG NSGS02 Reprogram device.
AUT AUTS03 Call telesales.
Click to expand...

Well... this makes sense if Suggestions and Questions are completely
independent. If a Suggestion applies to a particular Question, then
you should link to tblQuestions, probably by the two fields ProblemID
and QuestionNo.

This would let you deal with the question "Is there power to device?"
by providing an answer "Maybe it would work better if you plugged it
in" - which might not be an appropriate suggestion in other contexts.
Please tell me I interpreted this correctly, because I feel good about this,
and it definately makes more sense with my data. Even though I'm not
entering any new "per call" information, it allows me to add or remove any
new suggestions or questions. This is just first tier, so the tshooting is
not extensive. Am I ready to begin with the form now??? <g> (Thank you so
Click to expand...

You're getting a lot closer.

John W. Vinson[MVP]
Click to expand...
Well... this makes sense if Suggestions and Questions are completely
independent. If a Suggestion applies to a particular Question, then
you should link to tblQuestions, probably by the two fields ProblemID
and QuestionNo.
Click to expand...

I'm fixing the tables as suggested, removing the extra characters in the ID
Fields...
Okay, so linking tables can be done with the Relationship tool? I'm
assuming that I need to build all of my relationships after the tables are
done. If I don't use the relationship Tool, what do I use to create those?
Once the relationships are created, then what??? Keep in mind, the
questions/suggestions in the Application are average 5/5 each topic, so it's
not very extensive (just tier 1)
 
I'm fixing the tables as suggested, removing the extra characters in the ID
Fields...
Click to expand...

While you're at it, I'd suggest removing all blanks (and other special
characters if any) from your table and fieldnames. They work, but they
can cause trouble down the line.
Okay, so linking tables can be done with the Relationship tool? I'm
assuming that I need to build all of my relationships after the tables are
done. If I don't use the relationship Tool, what do I use to create those?
Click to expand...

Huh!? You use the Relationships window FIRST, after the tables are
created but before you start entering data. The main purpose of
relationships is to "Enforce Relational Integrity" - that is, to
ensure that you don't have any "orphan" records, e.g. a Question
relating to a nonexistant problem.
Once the relationships are created, then what??? Keep in mind, the
questions/suggestions in the Application are average 5/5 each topic, so it's
not very extensive (just tier 1)
Click to expand...

Then create suitable Forms to enter data into the tables - I'd say a
Problems form with (guessing here, not sure of your current
relationships) two subforms, one for QUestions relating to that
problem, the other for Suggestions.

John W. Vinson[MVP]
 
John Vinson said:
While you're at it, I'd suggest removing all blanks (and other special
characters if any) from your table and fieldnames. They work, but they
can cause trouble down the line.
Click to expand...

I learned this on my last project, so I made sure there weren't any spaces
in this one either. Thanks for the heads up.
Huh!? You use the Relationships window FIRST, after the tables are
created but before you start entering data. The main purpose of
relationships is to "Enforce Relational Integrity" - that is, to
ensure that you don't have any "orphan" records, e.g. a Question
relating to a nonexistant problem.


Then create suitable Forms to enter data into the tables - I'd say a
Problems form with (guessing here, not sure of your current
relationships) two subforms, one for QUestions relating to that
problem, the other for Suggestions.

John W. Vinson[MVP]
Click to expand...

Once I finish entering the data in the forms I will be back knocking on
doors to set up the application the reps will use to ask and get answers
from. Thanks again tremendously.

Regards

~treysoul
 
Back
Top