"automated unmanned job" - the "processing database" would have an autoexec macro in it that kicks off the processing of the databases in some folder (uses DIR() to loop over the databases).  You'd just call it using something like /x:macroName.
Then maybe create a job in SSIS to run that... ?  I want to say I vaguely remember Danny Lesandrini posting something about that a long time ago. I might have to ask him.
In a nutshell, you have an Access "front end-ish" database that connects to (uses linked tables) other "source" databases, and walks the Fields collection in of some of the tables in there. (DAO fun). Then you can do something based on what Fields are in the collection.

Steve - say I create a job in SSIS that kicks off a non-SQL Server thing - like a script that just opens the Access database that contains the autoexec macro (basically "DatabaseX".. always in the same place)... I can just script that part in SSIS, and then Access takes over, right?