remove from drowdown when selected

[Guest]

I have column width .2";1" and bound to 1
whin you click the dropdown list the dropdown it shows the ID and the
RiskDesc.
This is ok

When I select from the list, the field only shows the ID and not the RiskDesc.
Pretty weird...


--
deb

Do you have your ColumnWidths set to 0.0";1.5"?? ...which should hide the 1st
column.

It removed the item from the dropdown list perfectly!!!

What a great thing!!!!

Now the field in the dropdown shows the ID and not the riskDesc. I tried
adjusting the column counts and column widths but it still only shows the ID
number and not the text RiskDesc.

Any suggestions?

Thanks for jumping in John. Give it a go Deb.

[quoted text clipped - 14 lines]

John W. Vinson [MVP]

--
HTH - RuralGuy (RG for short) acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com

 

[ruralguy via AccessMonster.com]

Not weird. It is because of the .2 in the 1st column. Why not 0"?

I have column width .2";1" and bound to 1
whin you click the dropdown list the dropdown it shows the ID and the
RiskDesc.
This is ok

When I select from the list, the field only shows the ID and not the RiskDesc.
Pretty weird...

Do you have your ColumnWidths set to 0.0";1.5"?? ...which should hide the 1st
column.

[quoted text clipped - 13 lines]

 

[Guest]

with 0";2" It does not take out the used fields, and when I close and reopen
the form, the fields are now blank. The dropdown shows items but not the
fields that were previously entered. They are in the table though.

When I have 1";0" it works great but I only see the ID an not the RiskDesc
so the user has no idea what was chosen.

Its making me crazy!!!!!!!!!

You should try this one, I can't figure it out.
--
deb

Not weird. It is because of the .2 in the 1st column. Why not 0"?

I have column width .2";1" and bound to 1
whin you click the dropdown list the dropdown it shows the ID and the
RiskDesc.
This is ok

When I select from the list, the field only shows the ID and not the RiskDesc.
Pretty weird...

Do you have your ColumnWidths set to 0.0";1.5"?? ...which should hide the 1st
column.

[quoted text clipped - 13 lines]

John W. Vinson [MVP]

--
HTH - RuralGuy (RG for short) acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com

 

[ruralguy via AccessMonster.com]

That IS weird! You still have the ColumnCount set at 2 correct? What version
of Access are you using? I wonder if you now have some corruption. Do a
Compact and Repair and then import everything into a new empty mdb and see if
you still have the same issue. If you do, the how about zipping up the db and
email it to me at Rural Guy at Wild Blue dot Net?

with 0";2" It does not take out the used fields, and when I close and reopen
the form, the fields are now blank. The dropdown shows items but not the
fields that were previously entered. They are in the table though.

When I have 1";0" it works great but I only see the ID an not the RiskDesc
so the user has no idea what was chosen.

Its making me crazy!!!!!!!!!

You should try this one, I can't figure it out.

Not weird. It is because of the .2 in the 1st column. Why not 0"?

[quoted text clipped - 11 lines]

 

[ruralguy via AccessMonster.com]

Deb sent me the db and now we know why it is strongly recommended that LookUp
Fields in tables *not* be used.

Deb, here's a link to read:
The Evils of Lookup Fields in Tables
http://www.mvps.org/access/lookupfields.htm

All they do is confuse the programmer!!!

with 0";2" It does not take out the used fields, and when I close and reopen
the form, the fields are now blank. The dropdown shows items but not the
fields that were previously entered. They are in the table though.

When I have 1";0" it works great but I only see the ID an not the RiskDesc
so the user has no idea what was chosen.

Its making me crazy!!!!!!!!!

You should try this one, I can't figure it out.

Not weird. It is because of the .2 in the 1st column. Why not 0"?

[quoted text clipped - 11 lines]

 

[Guest]

What would you do to fix my mess?
--
deb

Deb sent me the db and now we know why it is strongly recommended that LookUp
Fields in tables *not* be used.

Deb, here's a link to read:
The Evils of Lookup Fields in Tables
http://www.mvps.org/access/lookupfields.htm

All they do is confuse the programmer!!!

with 0";2" It does not take out the used fields, and when I close and reopen
the form, the fields are now blank. The dropdown shows items but not the
fields that were previously entered. They are in the table though.

When I have 1";0" it works great but I only see the ID an not the RiskDesc
so the user has no idea what was chosen.

Its making me crazy!!!!!!!!!

You should try this one, I can't figure it out.

Not weird. It is because of the .2 in the 1st column. Why not 0"?

[quoted text clipped - 11 lines]

John W. Vinson [MVP]

--
HTH - RuralGuy (RG for short) acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com