Page 3 - Data Type

I am not sure how to capture this warning from the db. I usually create my own code to prevent duplicates. Lets say I want to prevent duplicate values from being entered into the field "TestID". I would then add a code to the after update event of the field. It would look something like this:

If DCount("[TestID]","tbl_Test",[TestID]='" & Me.Test & "'") > 0 then

Msgbox "Duplicate Value Warning",vbInformation
docmd.RunCommand acCmdUndo
exit sub
end if
What this code does is right after the id number is entered, the db checks the table to see if the id already exist in "TestID". If it does, then a message will appear giving the warning. As the user clicks "ok" on the warning, the code then undo the initial entry and the code exits.

Hmmm seems a little complicated, im only looking to put an error message in my database because its practically the last thing i need to put in. Whats the simplist error message to implement with for instance dealing with peoples details, perhaps unrealistic DOB or something? Any suggestions and how to implement them will be appriciated.

Cheers

The simplist error message is the message "Error". Not really, there is no simple way around this. If you want to look for errors in any part of the data entry, you must decide what you want to look for. After that, you will have to think of a way to look for that, and that is with code. I can't think of another way that can be simpler

I'm sorry, I don't mean to be rude, but I've been following this thread from the beginning. It's like as soon as you get one part solved, you put up the next part to be solved. It's like you have no database experience at all, and that you are trying to get it built part by part. While I have no problem teaching people the basics of ms access, or watching others do so, I feel that one should study up on the basics.

Each of your problems should have been a new thread. From my perspective, you've monopolized Toyman's time with each new problem. I would venture to guess that he's spent at least an hour catering to your new problems. From a professional point of view, that would be $100-$200 worth of advice you have received.

Most of us that post solutions here are IT/IS professionals, and if the others are like me, time is a limited resource. Not only do I answer threads here, but I have countless aquaintences, friends, and family who want me to fix their problems, not to mention the extra hours I put in at work from time to time. We have no choice but to live 24 hours as an IT/IS professional.

Toyman is a premiere database professional, he knows his stuff. You can rest assured that whatever he tells you is good as gold. In this forum, I don't think there is anybody more knowledgeable, whether it be database design, vba function, form layout, etc. etc. The only person who equals his knowledge would be Don.

With that said, I think that you are taking advantage of the knowledge you are tapping. You should start new threads rather than say, ok that part works, how do I get this part to work? This gives others a chance to evaluate your problems, rather than monopolize one professional's time. That, and when you keep all your problems in one thread, the others (including myself) tend not to read past the first few posts.

If you have a 34 post thread, as it is now, we might read the first few posts and the last few posts..... we don't have time to track everything that was posted. Personally, I read the first post, maybe the next 2 and then the last post. This is why you should post each problem separately.

I appreciate all the help i have been given but with all respect this is a help forum. You make it sound like i have been disrespectful because only one person has mainly been posting in reply to me. I have only been using one thread because i dont like to clutter message boards with little problems. If i had done that then i would have probably got a similiar message to yours but with the title "Petty Problems" or something.

By posting another thread i would have to repeat myself many times and i figured that this saves time and effort because i can be consistent with my replies rather than starting afresh, if people only choose to read the first few and last few posts in a thread thats their choice but my questions have been on the last few posts anyway.

As for my database experience you are right, i dont have any, sorry to take this personal but my life is the main reason i havent had time to brush up on the basics but im not going to post all the details suffice to say i havent had the time due to some bad times going on in my life. This led me to find help from somewhere and after reading through some of the threads before i registered i realised this was a great forum and so i joined. I appreciate all the help being given to me and i intend not to "monopolize" any more time here now because it seems asking for help here now just comes down to taking advantage when the title of the forum is "Microsoft Access Help".

Thankyou Toyman, you have really helped me out a lot and iam very grateful for the help and time you have given me, and to the others that have helped in my other threads. I truly appreciate it.

You're taking this the wrong way. I'm sorry about the personal issues in your life.

You're right, it is a help forum, and my previous post was to "help" you get answers in these forums. When I see a thread such as this, I skim over it (too many posts to go thru).... I'm just saying that what happens if the person who's been helping you gets fed up and stops? Most of us will skip over this thread no matter how many times you bump it due to the number of posts.

In posting in separate threads, you will want to include fields that you will be working with, any code you may have already, and any error messages or incorrect output that you are getting. It's usually a good idea to include your table design too.

Even if you have 5 minutes here and 5 minutes there, you could be studying up on relational database theory.

I am not trying to discourage you from posting your database questions, I am trying to help you get them answered. Personally, it matters not, who helps you. I am trying to explain to you that when you tack new problems on the end of a solved problem, they are probably going to be overlooked by all of the other kind people who volunteer their time to try to teach others some of the knowledge they possess.

As far as real life issues that you may be going through, I empathize with you. Unfortunately, real life can be down right nasty from time to time.

At the top of this thread index there are stickies (permanent threads at the top) that can give you a lot of information. Or you can go >>HERE<< or >>HERE<<

It would definitely be worth your while to check out the stickies and links.

I couldn't say this any better. Through the few years I have been on this forum, I have received more help from members here than I have helped. As such, I really enjoy helping others hear as I feel this is a good way for me to pay back what I have gained from this forum. As far as a "premiere database professional" I am not. I am just a humble tech junkie who is absorbing alot from this forum. Each person writes a db differently and a lot of the people here in the forum have simpler approach to a problem than I do. You are not doing yourself any favor by sticking with one style of writing a db. There are a vast amount of knowledge here in this forum and you would do yourself a favor by letting others look at the same problem from another angle.