Searching the whole DB for a text field

  • Thread starter Thread starter Demon
  • Start date Start date
D

Demon

I have a large DB with many tables and oodles of records in each. I have
some config data that repeats throughout the DB but I don't know which
tables it might be in. Is there a way to do a 'find' or even 'find &
replace' of a text string over the entire DB?

This sounds like a really simple thing to do, but I can't figure out how to
do it (I am an access newbie).
 
I have a large DB with many tables and oodles of records in each. I have
some config data that repeats throughout the DB but I don't know which
tables it might be in. Is there a way to do a 'find' or even 'find &
replace' of a text string over the entire DB?

This sounds like a really simple thing to do, but I can't figure out how to
do it (I am an access newbie).

Well, it's not ordinarily something one would WANT to do. "A place for
everything, everything in its place" is a basic principle. What is the
nature of this config data, and how does it come to be scattered all
over the tables in unpredictable places?

I can't think of any *easy* way to do this; I think you'll need to
create queries on each table, with criteria to find the data in any
appropriate field (no point searching Number or Date fields for text
strings of course). You can then create update queries to replace it.
But it'll be tedious!
 
Well, it's not ordinarily something one would WANT to do. "A place for
everything, everything in its place" is a basic principle. What is the
nature of this config data, and how does it come to be scattered all
over the tables in unpredictable places?

It's a directory path. It occurs in at least 2 tables that I found manually.
It's not that it's necessarily all over the place, rather that I don't know
where else it might be - It is someone elses database.
I can't think of any *easy* way to do this; I think you'll need to
create queries on each table, with criteria to find the data in any
appropriate field (no point searching Number or Date fields for text
strings of course). You can then create update queries to replace it.
But it'll be tedious!

I thought I was just being a bit dim, but apparently not. I will jsut have
to search manually...
 
Back
Top