Is Access the right product for my need?

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

Guest

I am trying to create a database for keeping track of issues that need to be
fixed for a software help manual. I need a table that lists all problems
found, another for problems with their potential fixes, another for fixed
issues etc.... All info needs to be accesible to all members involved in the
process. My question is if Access is the best suited program for this?

Can info from one table be moved to another table by the user working on the
database and having all tables be updated once this happens? Or do I just
need one big table? Any suggestions/comments are appreciated.
 
Yes, but you would not move the data from one table to another in your
example.

You would have one table with the issues. Potential fixes (if only one per
issue) would simply be another field in that table. Fixed issues would not
move to another table, they'd simply have a "Fixed" checkbox marked, or a
"Resolved Date" filled in.

With a normalized database, you don't move the records around as the status
changes. If your field names or table names contain data (like fixed or
not) then you probably have a poor design. Instead, include fields as I
outlined. You can then build a query that pulls only unresolved issues with
no suggestions. Or a query to pull unresolved issues with suggestions, or a
query to pull only resolved issues. In short, separate and find records
using a query, not by moving them around.

Let us know if you need more specific help.
 
One table should do it. I would put 2 check boxes in it to show that the
issue has a potential fix of has been fixed. But I would have 3 memo fields,
1 for the issue, 1 for the potential fix, and one for the actual fix. This
way you don't need to create relationships and you can run queries to show
the potential and actual fixes.
 
Hi Bluecougar,
issues etc.... All info needs to be accesible to all members involved in the
process. My question is if Access is the best suited program for this?

Access is the perfect tool for this.
Can info from one table be moved to another table by the user working on the
database and having all tables be updated once this happens? Or do I just
need one big table? Any suggestions/comments are appreciated.

Information can be moved from one table to another. But information should
not move from table to table. You can delve into the theory on this, but
just conceptually, think of table as a *type* of information. Information
about the same type belongs in one table.

So to answer your question,
Or do I just need one big table?

Well if the information you're entering is of the same type, then it all
belongs in one table. For example, information about issues should go into a
table called tblIssues regardless of who enters it, who starts it, whether
it's outstanding, complete, on hold, etc. etc.


HTH,
Immanuel Sibero
 
Thanks for the quick reply. All info that I need to include in the DB is
located in several Excell spreadsheets, is there an easier way for me to
import it to Access with out having to copy and paste individual entries?
 
comments inline


bluecougar said:
I am trying to create a database for keeping track of issues that need to be
fixed for a software help manual. I need a table that lists all problems
found, another for problems with their potential fixes, another for fixed
issues etc.... All info needs to be accesible to all members involved in the
process. My question is if Access is the best suited program for
this?

Access is very well suited for the job. I'd use it without thinking
twice. Best??
Can info from one table be moved to another table by the user working on the
database and having all tables be updated once this happens?

No! each item of data appears exactly once in the database. You
use Forms and Reports to view and present it appropriately for the
task at hand.
Or do I just
need one big table? Any suggestions/comments are appreciated.

At the least you'd want two tables: Issues and Notes

tblIssue would name the issue and describe it fully. I also
include a Boolean status field indicating whether the issue is Open or
Closed.

tblNotes would be the many side of a one-to-many relationship with
tblIssue. The Note records would have a date field, a field for
action assignment and a memo type field for the complete description
or activity log and resolution or status of this issue at this time.

I typically use the Form/SubForm paradigm and have the notes sort in
descending order so the most recent note is the first one visible as I
look at this issue. I have one report to show only Issues that are
still open and another report to show all Issue activity for the
project. Again, the Notes sort Descending so that the most recent one
is at the top.

HTH
-
-Larry-
 
You can use "Get External Data" in the File menu of Access and import it
into a new table in Access, then you can use an append query to copy the
data from that table into your table. You may have some cleanup to do be
fore you run the append query. After that, you can delete the import table.
 
Will all info be available for all users in real time?

Absolutely.

In your other post, you stated that the data was in several Excel
spreadsheets. Access would combine all that data and make all of them
available in real time to multiple users... something that Excel can not
do.


Immanuel Sibero
 
When I try to import the files I can seem to "find" the Excel files, only
files that are displayed for import are other Access DB.
 
When you open the dialog box, There is a drop-down box at the bottom that
says "Files of Type". Select "Microsoft Excel" from that list.
 
Never mind my last post.

Rick B said:
You can use "Get External Data" in the File menu of Access and import it
into a new table in Access, then you can use an append query to copy the
data from that table into your table. You may have some cleanup to do be
fore you run the append query. After that, you can delete the import table.
 
Back
Top