ACCESS FEED: RE: [MS_AccessPros] Is there a better way?

Rabu, 19 Oktober 2011

RE: [MS_AccessPros] Is there a better way?

Isn't the join to the primary key of the Fare table? If so, you should not get duplicate rows.

Duane Hookom

MS Access MVP

________________________________
> From: terryomsn@msn.com
>
> Hi,
> I have a file that I'm importing. I'm trying to normal the data to put
> it into my DB. In a data file input row, I have two columns, PeakFare
> and OffPeakFare. The input data has thousands of rows with text values
> of "KCM01" or "KCM23" or whatever.
> Using a query, I join the data columns in the file with a Fare Table to
> pick up a FareID value to store in the DB. To process the two fare
> columns, I add two copies of the Fare Table to join with the two
> columns PeakFare nad OffPeakFare. The joins work well unless the
> PeakFare and OffPeakFare are the same values (KCM01 in both PeakFare
> and OffPeakFare) in the raw data. When that happens, I get duplicate
> rows in the query result whenever they are the same.
> I could make another pass to clean that column, but I'd like to one
> pass through to minimize future processing hassle (more than one query
> for a table).
> Is there better way than two passes?
> Thanks
> Terryomsn