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

Combo box LimitToList property setting of No - I still get MS Access error...

P: n/a
MLH
Combo box LimitToList property setting of No does not
prevent the MS Access error "The text you enter must
match an entry in the list" from popping up. What makes
this bad is that the error is not a capturable error.

My list has 2 fields: [Reason] and [ReasonCode]. The
2nd column is the bound column.

Here's the RowSource property setting:
Select [Reason],[ReasonCode] From [tblReasons];

I want the user to select a reason from the list, of course.
But I DON'T want the user to see a MS Access error
pop up in an app I rollout in a runtime environment built
using Access 2.0 and the ADT (Access Developer's
Toolkit). Any way to avoid this?
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"MLH" <CR**@NorthState.net> wrote in message
news:1g********************************@4ax.com...
Combo box LimitToList property setting of No does not
prevent the MS Access error "The text you enter must
match an entry in the list" from popping up. What makes
this bad is that the error is not a capturable error.

My list has 2 fields: [Reason] and [ReasonCode]. The
2nd column is the bound column.
A ComboBox that displays one column while being bound to another is
automatically "LimitToList = True". If you attempt to change it you should get
an error telling you that the setting is not allowed.

Here's the RowSource property setting:
Select [Reason],[ReasonCode] From [tblReasons];

I want the user to select a reason from the list, of course.
But I DON'T want the user to see a MS Access error
pop up in an app I rollout in a runtime environment built
using Access 2.0 and the ADT (Access Developer's
Toolkit). Any way to avoid this?


Some of the built-in messages are a bit cryptic, but this one is perfectly
clear. Why do you want to replace it? If you just want to eliminate the
"Microsoft Access" in the error's title bar just give your app its own
application title and then that is what the error box will display instead.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #2

P: n/a
MLH
Good suggestions, Rick. I'll have a go with them. My
workaround was a 1-liner on the KeyUp event...

Sub MyComboBox_KeyUp (KeyCode As Integer, Shift As Integer)
Me!MyComboBox = Null
End Sub

And I really didn't like it much at all. Thx.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxx

Combo box LimitToList property setting of No does not
prevent the MS Access error "The text you enter must
match an entry in the list" from popping up. What makes
this bad is that the error is not a capturable error.

My list has 2 fields: [Reason] and [ReasonCode]. The
2nd column is the bound column.


A ComboBox that displays one column while being bound to another is
automatically "LimitToList = True". If you attempt to change it you should get
an error telling you that the setting is not allowed.

Here's the RowSource property setting:
Select [Reason],[ReasonCode] From [tblReasons];

I want the user to select a reason from the list, of course.
But I DON'T want the user to see a MS Access error
pop up in an app I rollout in a runtime environment built
using Access 2.0 and the ADT (Access Developer's
Toolkit). Any way to avoid this?


Some of the built-in messages are a bit cryptic, but this one is perfectly
clear. Why do you want to replace it? If you just want to eliminate the
"Microsoft Access" in the error's title bar just give your app its own
application title and then that is what the error box will display instead.


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.