In actual fact, i want to have my own tool that extracts data from a
source and stores it in a separate databse for someone else to work
with.
The data volumes are pretty large so i want to create a single database
per table and then i'll link back to them in a central analysis tool.
So i'll look at transferdatabse as mentioned but i think that the most
effective way of managing the data sets i'm producing is to code the
import and either import direct to an external database or to import to
the working database and then move the data out to an external mdb.
Any other ideas that i might investigate while i look at
transferdatabase?
Thanks,
Rob.
jahoobob via AccessMonster.com wrote:[color=blue]
> Also, consider linking these table to the other databases unless you're
> concerned about the other db users screwing up the data.
>
> dkintheuk wrote:[color=green]
> >Ok I have a database application that collects data from sources and
> >procudes output tables.
> >
> >Once created these tables need to be moved to other databases.
> >
> >Do I...
> >
> >a) have to do it manually?
> >b) write some SQL to write the data to the other database (created in
> >code first)
> >c) use commands as yet unknown to me to transfer the data across
> >seamlessly.
> >
> >Any good ideas?
> >
> >Thanks,
> >
> >Rob.[/color]
>
> --
> Message posted via
http://www.accessmonster.com[/color]
