unwanted data entry

[Big tony]

I have a two field table, where the first fields allows a
user to choose from a drop down box a list of categories
(from a table).

Based on their choice of category, the computer runs a
macro (shown below) which gives them a choice of
subcategories to choose based on their first choice. In
both fields I have chosen limit to list, but somehow the
second field is still allowing data entrants to type into
the field. How do I stop this madness?


(SELECT [Diagnoses Categories].DXCategoryID, [Diagnoses
Categories].DiagnosesCategory FROM [Diagnoses
Categories]; )

 

[Allen Browne]

Perhaps the 2nd box already has a value in it, before you change its
RowSource? If so, the solution would be to SetValue to Null when you set the
RowSoruce.

 

[John Vinson]

I have a two field table, where the first fields allows a
user to choose from a drop down box a list of categories
(from a table).

Based on their choice of category, the computer runs a
macro (shown below) which gives them a choice of
subcategories to choose based on their first choice. In
both fields I have chosen limit to list, but somehow the
second field is still allowing data entrants to type into
the field. How do I stop this madness?


(SELECT [Diagnoses Categories].DXCategoryID, [Diagnoses
Categories].DiagnosesCategory FROM [Diagnoses
Categories]; )

Are you using a Form? or <yuck, PTOOIE!> Lookup fields?

If it's a Form, set the Limit to List property of the combo box to
True.

If it's a table datasheet with lookup fields... get rid of your lookup
fields and build a Form.

John W. Vinson[MVP]
(no longer chatting for now)

 

[tina]

Are you using a Form? or <yuck, PTOOIE!> Lookup fields?
LOL....John, i agree with you completely, but you're just hilarious. <bg>

 

[Lynn Trapp]

LOL....John, i agree with you completely, but you're just hilarious. <bg>

Actually, I think John needs to be just a little bit clearer on what he
thinks about Lookup fields. I'm a bit confused on whether he's for them or
against them...<veg>

 

[tina]

LOL....yeah, i've seen a lot of these ambiguous posts from him re Lookup
fields. <vbg>

 

[Lynn Trapp]

LOL....yeah, i've seen a lot of these ambiguous posts from him re Lookup

fields. <vbg>

Me too. I'm gonna have to talk to John about that. Or maybe he's listening
in... <g>

 

[Douglas J. Steele]

Me too. I'm gonna have to talk to John about that. Or maybe he's listening
in... <g>

John Vinson tells us
Lookup fields are from Satan.
Avoid at all costs!

(sorry, I couldn't think of a good pun, his other media... <g>)

 

[Douglas J. Steele]

John Vinson tells us
Lookup fields are from Satan.
Avoid at all costs!

(sorry, I couldn't think of a good pun, his other media... <g>)

Er, medium... <blush>

 

[Lynn Trapp]

John Vinson tells us

Lookup fields are from Satan.
Avoid at all costs!

(sorry, I couldn't think of a good pun, his other media... <g>)

<g> You can be sure he's in the process of coming up with a pun right now.

 

[tina]

but just once, i think he should come right out and tell everyone how he
really feels about them, don't you? no more of these wishy-washy comments!
<bg>

 

[John Vinson]

<g> You can be sure he's in the process of coming up with a pun right now.

I've got several... but none of them are suitable for mixed company!
<g>

John W. Vinson[MVP]
(no longer chatting for now)

 

[Lynn Trapp]

I've got several... but none of them are suitable for mixed company!

<g>

As my mother always used to say, "Excuses! Excuses! Excuses!" <g>