Short of reverse engineering the Access file format, I
don't think this is possible without having some sort of
programming running inside Access or an EXE (VB or C++).
One crude work around I can think of would be to create an
Access "template" file with your manual import process
encoded in it (either through a Macro or via VBA).
Then, when you wanted to create your new .mdb file
populated with the CSV data, first copy this raw
template .mdb to another new .mdb file, then launch the
new .mdb file with the command line parameter set to run
the code that will automatically import the CSV file (this
could be by running a Macro or by having some code
attached to a form, if you encoded your import process in
VBA).
This is a bit convoluted, but you can make it work without
human intervention. You will need to look up "command
line" in the Access help file to read up on the Startup
Command Line Parameter options, and probably use the Shell
command if you will be lauching all of this from within
another Access database. Without knowing more about your
situation, I can't be more specific.
I'm pretty sure this could all be done directly via VBA
code, too, and it might even be more robust. The first
step would be importing the CSV file (as above), then
programatically creating a new database object (the
new .mdb file), and finally copying the newly imported
table into this object.
That would be a better question for the Programming
newsgroup, though. I'm learing Java, and it's has totally
corrupted my recollection of Access' Object model.
HTH
Rob
Rob
