Re: Help!!! Autolookup
From: Mike Farmer (farmer.m_at_comcast.net)
Date: 02/12/04
- Next message: Mike Farmer: "Re: Help!!! Autolookup..SOLVED!!!!!!!!"
- Previous message: Cheryl Fischer: "Re: Displaying Record Numbers with out Navigation controls...."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 12 Feb 2004 02:37:24 GMT
John, thanks for your response. With lots of help from another expert,
I've gone in a different direction and I have been able to get
autolookup to work.
I'm still puzzled by your "should not exist" comments. maybe I failed to
explain myself properly.
The data base I'm working on has many tables, one of whch is a "Zipcode"
table containing over 4,000 zip codes along with the corresponding city,
state & county.
I have a "form" with many fields which polulates other tables. Three of
the fields are City, state & zip. When I go to fill out the form and I
come to the "address" information, I wanted to be able to enter a zip
code and "grab the city & state from the table. The same with the
physicians information. I wanted to be able to enter a physician's nane
and then grab the "specialty & designation from the physicians table. I
probably confused things by mentioning the the "zip codes" and the
"doctors specialty and desination" fields. These are two separate
tables, neither containing the same information.
Thank you for your kindness in responding. Now I have a new problem for
my next post.
regards,
Mike
> On Mon, 09 Feb 2004 19:00:58 GMT, Mike Farmer <farmer.m@comcast.net>
> wrote:
>>I am attempting to have certain fields automatically filled in (City,
>>State) when I enter the zip code. I have a number of tables that are
>>populated by the form and I also have a table that contains: zip code,
>>city, state, county. I've tried following the various instructions but
>>nothing works. I also want to be able to enter a doctors name and have
>>the form automatically fill in the designation and specialty. This
>>information is also contained in another simple table. No Primary Keys
>>used. Everything I read talks about "One To Many Relatioships" but
>>that does not seem applicable here as all of the specied info is one
>>table. Any help would be much appreciated.
John Vinson wrote:
>
> Relationships DO matter here. You're missing a key point about how
> databases *work*.
>
> The City, State, and County fields SHOULD NOT EXIST in this table.
> The Specialty and Designation fields SHOULD NOT EXIST in this table.
>
> You are making the very common assumption that you must have all the
> information you want to see as fields in one single table. This
> assumption is incorrect!
>
> Instead, store *JUST* the Zip, and just the Doctor's primary key ID
> (yes, every single table should have a primary key), in this table.
> Then create a Query joining your table to the zipcode table by Zip,
> and pull up the city and state from the zipcode table; join the
> Doctors table by DoctorID, and pull up the doctor's name, specialty,
> etc. from the Doctors table. This Query can be used as the source of a
> Form or a Report; you don't need to store the information redundantly
> in two separate tables.
>
> John W. Vinson[MVP]
> Come for live chats every Tuesday and Thursday
> http://go.compuserve.com/msdevapps?loc=us&access=public
- Next message: Mike Farmer: "Re: Help!!! Autolookup..SOLVED!!!!!!!!"
- Previous message: Cheryl Fischer: "Re: Displaying Record Numbers with out Navigation controls...."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
