G'day Chuck
I am by far a long way off MVP, and I'm certain you'll get a few responses,
but here's my 2 cents worth for free.
If you have BoundColumn set @ 1 then it will try and insert the Name, not
the Abv, that's why your getting the error message "Too Long"
What's happening is that you are attempting to insert the Name, not the Abv
into the field.
Have a questions.?
1. What do you want stored, the Name or The Abv.
Change it to this:
SELECT [tblState].[StateAbv], [tblState].[StateName] FROM [tblState];
2. Why does the user have to enter in three places.
You could use something like this in the AfterUpdate()
Me.Place_1 = YourCombo.Column(0)
Me.Place_2 = YourCombo.Column(0)
Me.Place_3 = YourCombo.Column(0)
Column(0) is correct, (0) is interpreted as the first column by VBA.
(Something along those lines) this will automatically populate the areas in
1 instance.
Though I am still intrigued as to why 3 times, couldn't you just add an
index to your "Abv field", then a One-to-Many Relationship could be
established.
HTH
Mark.
>I have an access form I have been using for four years without any
> major problems. Part of the data entry requires a user to enter a
[quoted text clipped - 29 lines]
>
> Chuck Buckley
ceb39@myway.com - 22 May 2007 03:26 GMT
> G'day Chuck
>
[quoted text clipped - 72 lines]
>
> - Show quoted text -
Mark:
Thank you for your response.
To answer your questions.
What do I want to store? I want to store the abv of the state.
Why does user have to enter in three places? The data which is being
entered into the database might represent three different locations.
In fact now that you ask that question, I think the number of times
the abv. is the same is only about 20% of the time.
Developed a couple of test databases and a test form which only
address the state abv. Your right, when I select the field which has
the abv in it, the whole name of the state is store in the field where
I thought the abv was going.
Will give your solution a try and see what happens.
Thanks a bunch.
Chuck