	Welcome to the "Almost Real Attachment Manager".  Almost real because
it only reattaches tables in .MDB  files, it does not handle external data
files, such as dBase or Paradox (yet).  You may try, but you will get an error
message, so don't use it on these.   

	What it DOES do, it does well.  It will attach tables across multiple
.MDB files, in any drive/directory, which is something that the other freebie
"table attach" programs I've seen don't do.  Other programs quit once they find
that the first attached table in the database is valid.  This one will check them
all.  The down side is that if you are using only one external .MDB this program
will prompt you for each table when you move it.  The up side is that if you
decide to move ONE (or two or three) of the tables in the data .MDB to different
.MDB's, this program will only prompt you for the one's that you have moved.  
This will allow you to painlessly split data .MDBs or move them around on networks.  

        I wrote this program because, aside from developing databases, I administer
several networks.  I have some large projects that store data in many large files,
where it is shared by many different apps.  The standard "one program.mdb/one 
data.mdb" model works well for smaller apps, but not when you have a sprawling
corporate database and dozens (or hundreds) of tables.

        The core code (IsTableAttached()) came from a file I found here called 
"_APP.ZIP", uploaded by Bruce Troutman (thanks, Bruce).  I modified his code to 
process one table at a time, rather than just step through all of the tables.  
Then I put my own wrapper on it by creating a temporary querydef which reads the 
MSysObjects table for objects with a [TYPE] value of "6".  I step through the 
records and pass tables to IsTableAttached() one at a time, where I test whether 
there is a need to reattach them.

        All you have to do is call import the "_Reattach" module into your database
and call the "CheckAttachments()" function from either the AutoExec macro or your 
own startup procedure.  All of your attached tables will then be validated each 
time your program is run.

        There are two additional databases files included here (not that they do 
anything).  They are called TABLE1.MDB and TABLE2.MDB.  Move them around to 
different directories, rename them or combine them to test this program.  Press 
the "TEST" button on the next menu to do this.

        This program is freeware.  Use it at your own risk, since there is 
ABSOLUTELY NO WARRANTY, PERIOD.  Any feedback would be appreciated.  When I 
get the time (aside from my real job as a consultant/network administrator/
programmer) I will figure out how to make this program manage external data 
tables.  I am uploading this "as is" because, looking at what I've seen so far, 
there's probably a need for it.

       Please forward all comments, suggestions, or contract programming 
offers (:>) to:

William Finck  76307,1570