mass renaming of Access objects

[Angie]

I am in the process of converting an Access database to SQL Server 2005 using
the MS SQL Server Migration Assistant for Access. It works great, but the
naming convention for all of the objects in the Access database include
spaces which is not so great for SQL Server. I received LOTS of warnings
during the conversion. I'd love to be able to rename these objects and all
their references (preferrably just concatenating and trimming out the spaces)
in mass rather than individually. Any suggestions?

 

[Douglas J. Steele]

Look into a third party product such as

Find & Replace: http://www.rickworld.com/products.html
Speed Ferret: http://www.moshannon.com/speedferret.html
Ucora's: http://www3.bc.sympatico.ca/starthere/findandreplace/

 

[Graham Mandeno]

Hi Angie

Check out Rick Fisher's Find and Replace utility:
http://www.rickworld.com/index.html

 

[Tony Toews [MVP]]

Check out Rick Fisher's Find and Replace utility:
http://www.rickworld.com/index.html

There is a means of programmatically filling in Rick's find and
replace table. So the original poster could run through the tables
and fields collection gathering up all the names and stuffing those
into a temporary table. Then, in a second field, in that table
assign the new names to the fields.

(All the while hoping you don't have duplicate field names in tables
otherwise you could get into an interesting mess if you wanted the new
field names to be different in the two tables.)

Once you've got that looking decent then feed that into Rick's
utility.

Note that I haven't done this myself. I just recall reading about it.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Graham Mandeno]

Hi Tony

(All the while hoping you don't have duplicate field names in tables
otherwise you could get into an interesting mess if you wanted the new
field names to be different in the two tables.)

Could this perhaps be why some of us have naming conventions? <smile>

 

[Tony Toews [MVP]]

Could this perhaps be why some of us have naming conventions? <smile>

This has been a problem in dealing with databases created by others in
the past. And yes, that's one of the reasons I came up with my
naming convention.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/