Front End and Back End Database Question

[WildlyHarry]

I have a built a database with a front end and back end application. The
front end allows the user to input/manipulate data on the back end so that
all users are working from the same record. On a quarterly basis, the users
are required to purge the database and start fresh. I have the code written
to build some back up tables and structures to allow for the import of new
data, and it almost works fine (see below).

DoCmd.OutputTo acOutputTable, "Authorities", acFormatXLS, "Authorities.xls",
True

DoCmd.CopyObject , "Authorities Backup", acTable, "Authorities"
DoCmd.CopyObject , "Authorities", acTable, "Authorities Structure"

When I run this code in the Front End it creates the blank "Authorities"
table that I am looking for. But it does not make any changes to the back
end tables, which is what I am trying to accomplish. Should I put this code
on the back end? Or is there a way that I can have the front end make the
changes I need to the back end? Thank you in advance for any help that you
can provide.

 

[Dennis]

In CopyObject, the destination will always be local to where the command is
issued.

 

[WildlyHarry]

Then that answers my question. I will have to put the code on the back end
to affect all front end users. Thanks.

 

[Jeff Boyce]

Before you journey much further down that path, what business need are you
attempting to satisfy by having the "old" data purged?

I'm not asking out of idle curiosity, but because folks new to relational
databases sometimes treat them as though they were just "spreadsheets on
steroids", and the notion of purging and reloading sounds like a
spreadsheetly thing to do.

More info, please...

Regards

Jeff Boyce
Microsoft Office/Access MVP