Error table/list from hexcode reference

Question

0.00/5 (No votes)

See more:

Hi,

What is the accepted way of generating/storing/accessing a large list of user errors when programming in VB.NET?

I have a many errors that I would like to report if they occur. I have the error headings, and descriptions in a list that correspond to a hex code.

I could build two string arrays, but I figured that's not the appropriate method of doing something like this and then there would have to be many blank entries where the hex code doesn't correspond to a valid error code. I could also do a very large case statement, but again, I'm not sure that's the appropriate method of doing this. I could build a table in runtime and do a search for the hex code and then display the corresponding columns.

I couldn't figure out what is the accepted procedure for doing this. Can someone please tell me what the correct approach is to error reporting in VB.NET, with regard to storing the error information.

Thanks,

Marco

Posted 2-Aug-14 22:58pm

bigbro_1985

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2014-08-02T23:04:00

Solution 1

If you are reporting errors to the user, then time is not a major issue: so you do what is "cleanest".
If you are using a hex code to be the "master" and looking for an appropriate header and description to present to the user, then I'd probably use one (or two) database tables as they are simple to access and simple to change.
If the headings are shared, then I'd use two tables: one for headings and one for hex-to-description translation that includes a foreign key to the heading table. And then use a simple JOIN to get both text strings from the hex value.

Posted 2-Aug-14 23:04pm

OriginalGriff

Comments

[no name] 3-Aug-14 6:54am

Hi OriginalGriff,

Thanks, I was wondering about that. What simple database format would you recommend I use, I mean what is the industry standard for this?

Thanks,

Marco

OriginalGriff 3-Aug-14 7:20am

If is a website - and VB.NET implies it is - it will depend on what you web host provides.
Most provide Sql Server or MySql, some also Access.

If it isn't, it depends on what else you are using. What does your app have access to or use for other things? Is multiuser needed? lots of variables!

[no name] 14-Aug-14 1:24am

Oh yeah, sorry I guess the question was a bit open ended there.

For the most part I'm doing single user, windows forms applications. I'm just curious what the typical approach for storing an entire application's error information would be.

OriginalGriff 14-Aug-14 3:10am

Depends on the programmer, and how many errors we are talking about: Many systems don't have a "central store" of error info, but just add a new message / code when they report it. Works well for small error numbers, but it can be a PITA if you are trying to collate them for the user documentation or for multilingual translation.

There is no "one way" to do this - much like the rest of computing! :laugh:

[no name] 14-Aug-14 4:09am

LOL, that's true! I'll have a look into PITA, I'm not familiar with that. Now that you mention multilingual support, it is actually something I want to look into in the near future.

Thanks!