Re: Find and Replace in the Whole Base

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If you have a field that is named after a specific student (?Mark?) and
after a specific activity ("TermPaper") and concerning a specific degree
program ("BA in Philosophy"), your table is NOT normalized. You have a
spread*** if the above is true, not a relational database table.

If the above IS true, spend some time looking into normalization and
database design before you do anything else:

http://home.bendbroadband.com/conradsystems/accessjunkie.html

If you don't, you will struggle to get Access to do simple things that it
can easily do, but only with well-structured data.

--
Regards

Jeff Boyce
Microsoft Office/Access MVP
http://mvp.support.microsoft.com/

Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/


"Telesphore" <tgNoSpam@xxxxxxxxxxxxxxxx> wrote in message
news:OhtZN$ROHHA.536@xxxxxxxxxxxxxxxxxxxxxxx
There is a table tblStudents(=tblÉtudiants) in which there are fields that
could be transfered to a new table that we would like to call tblDiplomas
(=tbl Diplômes). All the fields related to grades obtained by the
students,
for example the marks "A+" , "B", "C-"... in the field "TermPaperMarkBAPh"
(=BPhNoteTrvÉcrit) the marks for the term paper for his B.A. in
Philosophy.

I suppose that the creation of a new table is a kind of normalization of a
data base.

I tried "MDBSearch" from
http://www3.bc.sympatico.ca/starthere/findandreplace and "Replace9" from
http://www.rickworld.com but it did not work.


"Jeff Boyce" <JeffBoyce_IF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le
message de news: epj%23ZdPOHHA.5012@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the clarification. However, unless we know what kind of
information is being stored in these fields, and what the underlying
entity-relationship model is, that probably won't be quite enough of an
explanation. (Sorry, I don't understand ?French well enough to guess
what
might be in these fields.)

I asked my question because it is rare to need to "move" fields in a
well-normalized database. Is this part of the process of normalizing
your
database?

--
Regards

Jeff Boyce
Microsoft Office/Access MVP
http://mvp.support.microsoft.com/

Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/


"Telesphore" <tgNoSpam@xxxxxxxxxxxxxxxx> wrote in message
news:%23VoiljOOHHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
Thank you,

What I mean by "Simplify" is that we realized that some fields in the
table
tblÉtudiants should be better in creating a new table tblDiplômes, for
example the fields: MentionBPh, BPhNoteTrvÉcrit, MatriculeBPhLatran,
DateBPhObtention, and so on.

"Jeff Boyce" wrote:
"Simplify" is not one of the standard normalizing reasons I've run
across
for changing a database structure. If you'll provide a bit more
description
about your data structure, the newsgroup readers may be able to offer
suggestions that will give you greater use of Access'
features/functions.

...
"Telesphore" wrote in message
We simplified table A by creating table B.

We transferred 50 fields from table A to table B.

We removed these 50 fields from table A.

Is there a fast way to correct the original names of the fields in
the
queries and forms of the base? For example, how to replace in the
base
all
occurrences of tblA.Student by tblB.Student?






.

Quantcast