My company is a nationwide field service org. We have subcontractors across the US to service our customers things like: extending digital/analog circuits, break & fix POS system, troubleshoot in-house wiring related to telecom equipments such as csu/dsu, routers, etc..
Our trouble ticket system is currently both back and front end based in MS Access. My project is to migrate MS Access into MS SQL and write a front-end in ASP.NET (using Visual Studio .NET 2003). I've experienced with SQL and ASP only 6 months and moving to ASP.NET and handle this kind of big project is quite a challenge for me.
Anyways, my questions to all experts out there are: Can you direct me to any useful resources out there in order to help me to get a good start on this? I'm looking for more like architecture design of trouble ticket in enterprise enviroment. What sort of things do I need to watch out when coding in ASP.NET while multi-update accessing to the same ticket. I'm sure there's millions more things that I need to watch out, but can't think anymore for now.
Please help.
Any response would be greatly appreciated.
ThanhUnfortunately your question is just way too open ended. We could sit here and talk about 1,000,000 possible pitfalls for your application. I would suggest that you Google the heck out of: ASP.NET, .NET, VB.NET, C# and check out the starter kits here:
Starter Kits
Several applications that provide excellent samples of .NET code, architecture and so on. Try and get your arms around .NET a little bit and then come back with some more specific questions.
BTW- One of the starter kits is an issue tracker and might be similar to what you're faced with.
Thank you very much for quick reply, FrankWhite!
You're right, I need to get my arms around .NET much more.
Thanh
I just wanted to add that although it seems like a tall order - it can be done. I work for an Office equipment service shop. We do local service calls on equipment. I built a system ( first in Access, then ASP, and now .Net) that allows us to enter a trouble ticket, assign a tech, and track the call progress. I'm using .Net and SQL 2000. There is an Issue tracker starter kit - this should give you a good starting point to draw ideas from, along with the time tracker starter kit. Since you already hace the Access version - you should start with that. Import your tables into SQL and build the web based front end using the acces forms as a guide. Then you can tweak it to what you need.
You can do it...
HTH
Thanks for your post, UncleB.
Yeah... I was gonna code in ASP for front-end because I felt comfortable, but ASP.NET is so attractive even though I'm just .NET beginner. I'm more confident now that "can be done" with ASP.NET.
0 comments:
Post a Comment