"Like" criteria for update query

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My friend and I have been keeping separate reference lists of our own, so I
would like to combine them to view the data side by side.

After appending the records into one table, I'm having difficulty with the
codes where [Station] is null, or does not have a perfect match with
[Station2], or vice versa. If it weren't for my friend having duplicates in
the
Code: 
 field, I could do a simple update query.

Using the example below:

I would like the first two "ALC" records combined into one automatically,
since in reality they are identical, my friend just added some extra info in
the [Station2] field. Can I use some sort of "Like" criteria for an update
query (i.e. if [Station] is "Like" [Station2] then...)?

In case you're wondering, the last ALC record will have a null entry for
[Station].

[Code]-----[Station]--------------------------------[Station2] <---field names
|ALC|-----|Altamont, CA|-------------------------------- | null value |
|ALC|-----| null value |-------------------------------- |Altamont, CA (UP) |
|ALC|-----| null value |-------------------------------- |Alturas, CA (UP) |
 
Make copies of the two lists.

Update the two lists so that they match.

For example, update "Altamont, CA" to "Altamont, CA (UP)"

You will probably find that you can do 80% of the updates
with just a few update queries:

IIF([station] & " (UP)" = [station2], [station] & " (UP)",[station])

then fix up a few obvious exception by hand.

Then just append the records which are not duplicates.

Yes, you can use LIKE as criteria for an update query. What
exactly is your question?

(david)

Cheese said:
My friend and I have been keeping separate reference lists of our own, so I
would like to combine them to view the data side by side.

After appending the records into one table, I'm having difficulty with the
codes where [Station] is null, or does not have a perfect match with
[Station2], or vice versa. If it weren't for my friend having duplicates in
the
Code: 
 field, I could do a simple update query.

Using the example below:

I would like the first two "ALC" records combined into one automatically,
since in reality they are identical, my friend just added some extra info in
the [Station2] field. Can I use some sort of "Like" criteria for an update
query (i.e. if [Station] is "Like" [Station2] then...)?

In case you're wondering, the last ALC record will have a null entry for
[Station].

[Code]-----[Station]--------------------------------[Station2] <---field names
|ALC|-----|Altamont, CA|-------------------------------- | null value |
|ALC|-----| null value |-------------------------------- |Altamont, CA (UP) |
|ALC|-----| null value |-------------------------------- |Alturas, CA (UP)[/QUOTE]
|
Click to expand...
 
Back
Top