By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,297 Members | 1,390 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,297 IT Pros & Developers. It's quick & easy.

Use of INSERT INTO

P: n/a
Hello, all, and thank you for your assistance in the past...

Using Access 2000 from the Office 2000 Professional package...

I use INSERT INTO to add some information to a table...nothing fancy. The
statement does what I want, but when it executes, Access
produces a warning telling me that I'm "about to add one record..." to the
table, and that I can't use "Undo" to delete it. And that's fine.

This is the line that runs...it is the only line in the button's "Click"
event that does any table manipulation -

DoCmd.RunSQL "INSERT INTO tblGuestInfo...show field names and values
here..."

I've not had much experience with error handling, so my question is sort of
multi-part -

1. Is it possible to write an error handler around this particular message?
2. Where might I look for samples for this situation?
3. In general, how does one decide when error-handling is really
required...the possibilities for things to go wrong are endless. The
likelihood of
some things going wrong is greater than others, though. Any good
references out there?

TIA
Steve E.



Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Check Help for "Set Warnings".

"Serious_Practitioner" <Se************************@att.net> wrote in message
news:o%********************@bgtnsc05-news.ops.worldnet.att.net...
Hello, all, and thank you for your assistance in the past...

Using Access 2000 from the Office 2000 Professional package...

I use INSERT INTO to add some information to a table...nothing fancy. The
statement does what I want, but when it executes, Access
produces a warning telling me that I'm "about to add one record..." to the
table, and that I can't use "Undo" to delete it. And that's fine.

This is the line that runs...it is the only line in the button's "Click"
event that does any table manipulation -

DoCmd.RunSQL "INSERT INTO tblGuestInfo...show field names and values
here..."

I've not had much experience with error handling, so my question is sort of multi-part -

1. Is it possible to write an error handler around this particular message? 2. Where might I look for samples for this situation?
3. In general, how does one decide when error-handling is really
required...the possibilities for things to go wrong are endless. The
likelihood of
some things going wrong is greater than others, though. Any good
references out there?

TIA
Steve E.



Nov 13 '05 #2

P: n/a
Hello, Larry -

Thank you for your help. I didn't see that when I was looking through
"Help"...don't know why.

Thanks again.
Steve E.
"Larry Linson" <bo*****@localhost.not> wrote in message
news:h4****************@nwrddc01.gnilink.net...
Check Help for "Set Warnings".

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.