Copy tables from remote machine?

[ShyGuy]

I have a routine that creates a new database and then copies a couple
of tables to the new database as backups. It works fine but I want to
split the database and run this routine from a machine that does not
have the actual tables on it. I am using the following

DoCmd.TransferDatabase acExport, "Microsoft Access", "Backup.mdb",
acTable, "TableName", "TableName"

Is there a way to use this and get the tables from a different
machine?

Thanks for any help.

[Pieter Linden]

ShyGuy <sh****@shytown.com> wrote in message news:<ge********************************@4ax.com>. ..

I have a routine that creates a new database and then copies a couple
of tables to the new database as backups. It works fine but I want to
split the database and run this routine from a machine that does not
have the actual tables on it. I am using the following

DoCmd.TransferDatabase acExport, "Microsoft Access", "Backup.mdb",
acTable, "TableName", "TableName"

Is there a way to use this and get the tables from a different
machine?

Thanks for any help.

What if you use the UNC path instead of just "Backup.mdb"? e.g.

\\SomeComputer\SomeFolder\Backup.mdb

[ShyGuy]

On 12 Oct 2004 20:50:05 -0700, pi********@hotmail.com (Pieter Linden)
wrote:

ShyGuy <sh****@shytown.com> wrote in message news:<ge********************************@4ax.com>. ..

I have a routine that creates a new database and then copies a couple
of tables to the new database as backups. It works fine but I want to
split the database and run this routine from a machine that does not
have the actual tables on it. I am using the following

DoCmd.TransferDatabase acExport, "Microsoft Access", "Backup.mdb",
acTable, "TableName", "TableName"

Is there a way to use this and get the tables from a different
machine?

Thanks for any help.

What if you use the UNC path instead of just "Backup.mdb"? e.g.

\\SomeComputer\SomeFolder\Backup.mdb

Thanks for the reply.

The Backuip.mdb is the database that is created on the drive of the
machine that is doing the backup (Drive A). I want to create this on
that drive so that if the machine that has the back end (Drive B)
crashes I will have the backup on Drive A. The problem, I think, is
getting the transferdatabase to take the tables from the backend, on
tDrive B, and "export" them to the "backup.mdb on the Drive A.

[Pieter Linden]

ShyGuy <sh****@shytown.com> wrote in message news:<mi********************************@4ax.com>. ..

On 12 Oct 2004 20:50:05 -0700, pi********@hotmail.com (Pieter Linden)
wrote:

ShyGuy <sh****@shytown.com> wrote in message news:<ge********************************@4ax.com>. ..

I have a routine that creates a new database and then copies a couple
of tables to the new database as backups. It works fine but I want to
split the database and run this routine from a machine that does not
have the actual tables on it. I am using the following

DoCmd.TransferDatabase acExport, "Microsoft Access", "Backup.mdb",
acTable, "TableName", "TableName"

Is there a way to use this and get the tables from a different
machine?

Thanks for any help.

What if you use the UNC path instead of just "Backup.mdb"? e.g.

\\SomeComputer\SomeFolder\Backup.mdb

Thanks for the reply.

The Backuip.mdb is the database that is created on the drive of the
machine that is doing the backup (Drive A). I want to create this on
that drive so that if the machine that has the back end (Drive B)
crashes I will have the backup on Drive A. The problem, I think, is
getting the transferdatabase to take the tables from the backend, on
tDrive B, and "export" them to the "backup.mdb on the Drive A.

Why would TransferDatabase not work? Did you try it? If you did,
where's the code and what happened when you tried it? Have you played
with using the RENAME function from within a dummy DB? (so it can
effectively copy the database from one location to another)? Oh, and
do all this stuff on a backup. Don't want to hear "you rotten
so-and-so, you ruined my database..."

[ShyGuy]

On 13 Oct 2004 21:52:18 -0700, pi********@hotmail.com (Pieter Linden)
wrote:

ShyGuy <sh****@shytown.com> wrote in message news:<mi********************************@4ax.com>. ..

On 12 Oct 2004 20:50:05 -0700, pi********@hotmail.com (Pieter Linden)
wrote:

>ShyGuy <sh****@shytown.com> wrote in message news:<ge********************************@4ax.com>. ..
>> I have a routine that creates a new database and then copies a couple
>> of tables to the new database as backups. It works fine but I want to
>> split the database and run this routine from a machine that does not
>> have the actual tables on it. I am using the following
>>
>> DoCmd.TransferDatabase acExport, "Microsoft Access", "Backup.mdb",
>> acTable, "TableName", "TableName"
>>
>> Is there a way to use this and get the tables from a different
>> machine?
>>
>> Thanks for any help.
>
>What if you use the UNC path instead of just "Backup.mdb"? e.g.
>
>\\SomeComputer\SomeFolder\Backup.mdb

Thanks for the reply.

The Backuip.mdb is the database that is created on the drive of the
machine that is doing the backup (Drive A). I want to create this on
that drive so that if the machine that has the back end (Drive B)
crashes I will have the backup on Drive A. The problem, I think, is
getting the transferdatabase to take the tables from the backend, on
tDrive B, and "export" them to the "backup.mdb on the Drive A.

Why would TransferDatabase not work? Did you try it? If you did,
where's the code and what happened when you tried it? Have you played
with using the RENAME function from within a dummy DB? (so it can
effectively copy the database from one location to another)? Oh, and
do all this stuff on a backup. Don't want to hear "you rotten
so-and-so, you ruined my database..."

Sorry I haven't replied sooner. I was away for a bit.
When I tried the TransferDatabase it seeme to just transfer the link
to the remote table, not the Table itself. Not sure what you mean
with RENAME and dummy DB.. Are you saying that I have to copy the
remote (backend) DB to the local machine and then do the transfer?