Question updating mdb file outside of access using dumpfile?

[Nirious]

Hi,

I need to update an existing base mdb database on approximately 3000 pc based systems.
According to the configuration of the particular system, I have multiple possible changes that change in the database.

I was wondering if there exists a program that alows me to:

1)dump the access file to a text file containing all the sql commands that would need to be called in sequence to get the same mdb file (if sent to a new one)
I mean like what you can do in mysql, but for access.

2)Eventually I will modify these "dump files" and send them to each machine to update the parts that I want using the (same? ) program from the commandline. Think of them as update scripts, containing a sequence of sql commands to put the mdb file up to date.
based on the configuration of the pc, I would send diffrent snipets from the dump file to the mdb database.


So....
Does this exist already?
1)tool to generate a dump file from mdb containing "access" sql commands
2)commandline tool that accepts two parameter
a)the path to a mdb file to update
b)a text file containing a sequence of "access" sql commands and executes them on the mdb


Just trying to not reinvent the wheel

 

[G37Sam]

What exactly do you need to update? Data? Tables? Forms?

Are the 3000 PC's linked to one backend or is each one a single independent mdb file?

 

[Nirious]

I only need to update data. No changes to schema.
Just delete some rows, insert some rows, update some rows on a couple of tables.
There are no forms in the mdb.
The 3000 pcs have each their own "personal" db with local info contained in it.
Though they all start from the same mdb file that is embedded in the image.
So basically schema is the same for all, data is different for all.

Worst case scenario I will need to write a script to update it line by line using adodb.
Just hope it doesn't come to that
I program like I described above would really come in handy

 

[G37Sam]

Well, since every PC has it's own separate data, then something will have to be executed 3000 times unfortunately.

Whether its a Query, SQL Statement, DAO or ADO code, that is up to you