Run a Series of mdbs automatically 5

[alr0]

Happy Friday All,

Using Access 03 with Win XP Pro:

I have several mdbs that each perform a function. Now that these work I would like to have a master mdb that starts one of these mdbs and when it is finished starts the next one until they have all run. I presume that I will have a form where users can enter the full path of each mdb to run.

I am interested in my VBA options to open each listed file as soon as the last one is completed until all listed files have been run.

Thanks for any insights,

alr

_____________________________________
If a large part of intelligence is the ability to generalize, it is ironic that a large part of what we call wisdom is the ability not to generalize.

 

[MichaelRed]

It is hard to understand the full needs . requirements from fragmentary posts so this is NOT a critique. It is, however, a highly unusual approach to the use of a database. Even MS Access would seem to have adequate capability and capacity to handle the process as I understand the fragmentary descriptions within the thread. Particularly the part about reading text files into tables and using the error(s) as a validation of the file integrity. BNeen there, done that - but without the need for seperate databases. Importing test files (in particular) is hazzardous to the health and integrity of the overall db, so caution is appropiate. I ALWAYS import into a temporary structure (could be table or an array) of all string types. This assures that all info actually gets into the desired temporary structure. V&V can then be applied to not just the file, but to each individual field. Errors or other discrepancies can be collected and documented at a much finer level of detail and returned to the appropiate resource manager. If errors/discrepancies are noted, either the entire file or individual records may be excluded from further processing. Where files/records are accepted, they are easily transfered to the appropiate location(s).

You mention the plethora of seperate database files is necessitated by resource limitations. The above approach would seem to actually reduce the overall resource requirements, as the part which does the import only needs a set of deffinitions of the various imports (e.g. the file list), what to expect from the various imports (the verification and validation requirements(at what ever level of detail useful / required), the 'destination' of the validated information (whole file or individual records). Of course some of the flow control logic mentioned in earlier posts is still required (e.g. the variation of which portions to be run for any specific session), but the overall process would seem to be both more efficient and easier to maintain.




MichaelRed