Help redesign a call tracking system, conceptaul question
Posted: Fri Sep 10, 2010 5:40 pm
Hello all,
I'm new to php/mysql but not new to programming or sql in general but I'd like some conceptual advice here from some people with experience.
My task is to try and create a better call tracking system than the one our vendor uses. They have a web based system that is just horrendous and looks like it was adapted from something else so many fields do not match up correctly. The first issue is we will still have to use this website to submit the call to the vendor but I also want to have a copy of the call submitted in our own local database so we can track information and updates that the current vendor's call system doesn't track. I'm not in any real time crunch right now and am working on this on my spare time at work so I want to try and do it right other than slap something together in one of the other languages I know.
Based on the above information how would you guys handle the duplicate posting of the information? I have a few thoughts on this, my first one is to write in JavaScript a redirect page that after the call information is entered into my own help call page it redirects the user to the vendor web page and fills out the information for them. I'm not sure if this will work though as it has been a very long time since I have wrote java script, and now that I think about it the vendor website has a password page at the beginning.
My other thought was to ask the vendor if I can connect to their database and submit the information directly just like they do in the help call system. I'm thinking that I would probably be told no to this.
What else can you guys think of to help avoid making a person enter the same help call twice?
Thank You for your time,
-Nick
I'm new to php/mysql but not new to programming or sql in general but I'd like some conceptual advice here from some people with experience.
My task is to try and create a better call tracking system than the one our vendor uses. They have a web based system that is just horrendous and looks like it was adapted from something else so many fields do not match up correctly. The first issue is we will still have to use this website to submit the call to the vendor but I also want to have a copy of the call submitted in our own local database so we can track information and updates that the current vendor's call system doesn't track. I'm not in any real time crunch right now and am working on this on my spare time at work so I want to try and do it right other than slap something together in one of the other languages I know.
Based on the above information how would you guys handle the duplicate posting of the information? I have a few thoughts on this, my first one is to write in JavaScript a redirect page that after the call information is entered into my own help call page it redirects the user to the vendor web page and fills out the information for them. I'm not sure if this will work though as it has been a very long time since I have wrote java script, and now that I think about it the vendor website has a password page at the beginning.
My other thought was to ask the vendor if I can connect to their database and submit the information directly just like they do in the help call system. I'm thinking that I would probably be told no to this.
What else can you guys think of to help avoid making a person enter the same help call twice?
Thank You for your time,
-Nick