[AccessD] ADH2K - utils - TsiNameFixup90

Sad Der accessd666 at yahoo.com
Wed Jul 20 08:00:27 CDT 2005


Hi group,

I was browsing the CD A2K Developers handbook volume
2: Enterprise Edition.

I found the following file in:
Z:\Other\TSI\AutocorrectWizard\TsiNameFixup90.dll

It had a readme file (text is below).
However I 'm confused on what to do with the DLL.

I've created a module in wich I instantiate a
TsiNameFixup90.dll object

Public objAutoCorrect As TsiNameFixup90
Set objAutoCorrect = New TsiNameFixup90

The problem is that the objAutoCorrect seems to have
no public interface i.e. there are now
properties/methods when I try the intellisense.

Does anybody know how I can use this DLL?? 

BTW: The AutoCorrect function is really cool!!!!!
SD
------------------------------------------------------
README.txt
------------------------------------------------------
The Access 2000 "Name AutoCorrect" feature is a pretty
cool one. The following is 
an excerpt from the Access 2000 Help topic "What Name
AutoCorrect fixes and 
doesn't fix in an Access Database.":

"In Microsoft Access 97 and previous versions, if you
rename a field in a table, you 
find that the objects based on that field no longer
display the data from that field. 
Microsoft Access 2000 automatically corrects common
side effects that occur when 
you rename forms, reports, tables, queries, fields,
text boxes or other controls in a 
Microsoft Access database. This feature is called Name
AutoCorrect."

As the help topic discusses later on (you can look at
it directly for details) Access 2000 
Name AutoCorrect does not do every possible kind of
name fixup you could possibly need 
when you change the name of an object, field, or
control.  But it does handle many of the 
scenarios that you might want it to.

However, in order for it to work, you need two things:
1) The Tools|Options properties for Name AutoCorrect
must be set to True for the 
database so that Access knows to update the name maps
for the various objects and to
actually do renames as it finds that it needs to.
2) The "name maps" for the various objects must be up
to date.

If you have turned off the properties in #1 above, or
if you are converting a database
from a prior version, your name maps may be incomplete
or non-existent. The only way to
update them is to turn on the properties and then open
each table, query, form, and report
in design view and save.

Thats what this ComAddIn does! It does the work to set
the properties and open/save/close
all of the objects. Certainly easier than doing it all
yourself.

Source is also available for your viewing pleasure.
Its a nice, simple example of a ComAddIn
for Access 2000 that interacts with the Access menus
and object model.

Enjoy!

Michael Kaplan
Trigeminal Software, Inc.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



More information about the AccessD mailing list