Auto Enter County, State & Zip after entering City

Combo =  Combo Box (also known by many people as Drop Down)

Bob Larson, Former Access MVP (2008-2010) http://www.btabdevelopment.com (free Access tools, tutorials, and samples)

I am so very sorry. I don't even know what a combo is!

I need to explain what Level 1 training is:

my book is from www.elementk.com the title is Microsoft Office Access 2010 Level 1 (first look)

I basically got a overview of the fundamentals of Access & how things basically worked. We had to use their pre-made data and tables. The only 'design' we did in our 1 day class was using the Wizards. While there were only two of us in the class, and we were both from the same non-profit, the instructor still only read thru the book. She was unable to help us with specific questions or even give us a start on our database. We got to play with and modify existing data and the existing elements, but never really created anything from scratch. I'll be lucky if I can remember how to do a drop down list, let alone remember where I can use one since we went over it so very fast in the one day class!

Thank you all for your patience with such a novice. I think I might be better off with no knowledge as it seems the little bit I got from the class is only hurting me since I keep thinking I should be able to do more than I really can....

Normally I don't use a zip code entry and all as David Fenton has said as well.  I do normally store the state and zip code together with the city in the record.  But if you are wanting other information based on zip code to pre-populate then I had suggested that was a bit outside of the realm of normalization.  But I am wondering, if you really want to store it, what harm is there (none really).  So I back track a bit on the normalization argument as it is sometimes okay for a little denormalization to make things work better.  Since the cities aren't going to change, the data is pretty safe to store.

So, you can use a combo to select the city and populate the rest by using this in the AfterUpdate event of the combo:

Me.State = Me.ComboName.Column(2)

Me.City = Me.ComboName.Column(1)

Me.County = Me.ComboName.Column(3)

That is zero based so the 2nd column is 1, 3rd is 2, etc.  You set up the combo row source to include everything from the zip code to the county and then set the combo column count to 4 (if there are 4 columns, which I'm assuming based on Zip Code, City, State, and County. 

Bob Larson, Former Access MVP (2008-2010) http://www.btabdevelopment.com (free Access tools, tutorials, and samples)

:) I did get a chuckle about the Zip Code argument :)

Funny thing is, we do have Two Separate Cities (15 miles apart) with the SAME Zip Code AND a larger city with more than one Zip Code... But that larger city is in ND only in our service area for one service. ALL of our MAJOR service area has a finite number of cities in 3 counties in 1 state. I just get tired of typing MN and looking up the zip code if they didn't write it on the form...

Anyway...I will look into figuring out how to break down the couple hundred entries in my Individuals Table and break out the Address for a Households Table. That actually makes a lot of sense for many reasons.

Should I do the same PK code system breakdown for the city, state & zip?

THANKS!!!

Hopefully, everyone learned a little something here!!! :)