Help with my Helpdesk

[Chimp8471]

i am after a little help with a database, for college.

i posted something a while back on the forum, it is referencing a helpdesk i now need to build it...

i have some tables that i need to link together, which i need some help with.....

table setup as follows

but i also need to work out how i am going to get this whole thing to work properly.


the main issue is, i need to be able to assign jobs to various technicians, and when the next technician becomes available he is then assigned the job...the trouble is i have no idea how i am going to

any suggestions, would be happy to forward my structure to you if ya want to see it??

i have attached the database below:-

cheers

Andy

 

[a.sinatra]

Will work on it when i get home, but you can start by removing the space in "Workstation Name" Just playing with you, but you know you will be helped, have a great day!
________
Ford Cht Engine

 

[a.sinatra]

Alright, from what i found, you totally have to re-work that tbl structure. I am windering if you even made an erd?
________
Macintosh games

 

[Chimp8471]

bit confused here, i built my tables on info gathered on this and other forums, what exactly is wrong with my tables ??

 

[a.sinatra]

Alright... The information in some tables should be in others. Take for instance "Tbl_HelpDesk" it has items that should be in "Tbl_Ticket"

And...

Tbl_UserInfo contains fields "LoginName" and "Password" what if that same user had more than one computer with diff logins and passwords; your db wouldnt be efficent. Those fields should be placed in "Tbl_Workstation"

Do you kind of understand where i am going out, i mean in a sense i would like to help you re-design it, but time is money, and i ain't got either!
________
Indica Strains

 

[Chimp8471]

Do you kind of understand where i am going out, i mean in a sense i would like to help you re-design it, but time is money, and i ain't got either!

that makes two of us, i am just a poor student trying to work my way through this.........needing all the help i can get

i do kind of get what you mean, but aint fully sure........

 

[a.sinatra]

Hah Alright

I may have time tomarrow to help you, i glad you get where i am coming from.

When is this due? I'll try to help you asap though.

Have a great day,

Anthony Sinatra
________
HERBALAIRE VAPORIZER

 

[Chimp8471]

i have about 2 weeks to get this sorted.......

thanks so much

 

[The_Doc_Man]

One of the most important issues I try to explain to folks here is that when you get a complex model like this, you are in essence mapping your Access DB to a model of your (proposed) business. And for that there is a simple yet amazingly pervasive rule: If you cannot do it by hand on paper, you will never do it by machine in a database.

The very first thing I would do is get some grid paper and build yourself a couple of "fake" entries for every table.

Now manually, using sticky notes if need be, step through the process of accepting a problem.

Hint: To assign a problem, you need to have a form in which a tech closes a problem and requests assignment of a new one. You can assign this new problem by updating the tech record from the problem ID assigned by a find-first query (look in the Help files for Find First queries). Of course, when you assign a problem to a tech, in this model it appears that you also must assign a tech to a problem; otherwise you will just hand out the same problem over and over again.

Anyway, this appears to be a model in which the tech works the problem until it is finished and never hands it off to anyone else. The problem gets attention once assigned and is never suspended or put aside for any reason.

If that isn't what you wanted, then your table design is deficient in that it lacks the tables that would allow you the options I said you didn't have.