Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Steve Takach	Reported as Irrelevant
Written: 5/17/2005 1:10 AM
This solved all my problems. The error message ado.net returns should be more informative (or access should not allow reserved words as column names) as i spent countless hours trying to work this one out.

MeToo	Reported as Irrelevant
Written: 8/2/2005 10:51 PM
I should have searched the internet ealier instead of wasting some hours this night on this issue :-( After changing column names everything works now :-)

Anonymous User	Reported as Irrelevant
Written: 2/15/2006 4:45 PM
Thank you so much! I have spent several hours with this problem and it's now fixed thanks to you. I guess that this may be one reason for using appropriate naming conventions for everything. I have learned my lesson.

satya - satya_akula NOSPAM-AT-NOSPAM reiffmail.com	Reported as Irrelevant
Written: 3/3/2006 4:37 AM
put that reserved word in square brackets([])in query expression then ado.net won't give u any error

Jenice - vampirakhell NOSPAM-AT-NOSPAM hotmail.com	Report As Irrelevant
Written: 11/28/2007 10:04 PM
hi, my english is poor but i can't leave of this page without try tell us: this page solve all my problems, thanks, i can continue with my homework now... every day we can learn something new.