Deleting Objects in another database (.mdb)

[Craig]

Hello. I have built a pretty nice little db (Access 2003) for a customer of
mine, and, over time, would like to send him "updates" as I tweak and
streamline things. I'm thinking along the lines of an "update.mdb" that
would contain the updated objects (queries, forms, reports) and a sub that
would delete these objects from his existing .mdb file and export the new
ones to it. Then he could just delete the update.mdb when done.

"Sending" the new objects doesn't seem to be a problem, using
docmd.TransferDatabase, etc., etc., but I haven't figured out how to delete
all the existing objects prior to sending over the new ones.

I use DAO quite a bit within a "current" db, but haven't used it yet to work
with/manipulate another db. I'm guessing this is the route I need to take?

Thanks much for any suggestions/tips/solutions anyone can provide! Greatly
appreciated!

 

[Tony Toews [MVP]]

Hello. I have built a pretty nice little db (Access 2003) for a customer of
mine, and, over time, would like to send him "updates" as I tweak and
streamline things. I'm thinking along the lines of an "update.mdb" that
would contain the updated objects (queries, forms, reports) and a sub that
would delete these objects from his existing .mdb file and export the new
ones to it. Then he could just delete the update.mdb when done.

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute the entire FE MDB to the client possibly as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Craig]

Tony,

Thanks much for the response. I am familiar with the Front End/Back End
solution, but my customer prefers working with a single file (I offered the
FE/BE solution).

I have also thought of just sending an "update" .mdb with the updated
queries/forms/reports and just importing their existing tables, but that
would mean they would have to start using the "new" .mdb, adjusting any
shortcuts they've created.

Aside from the FE/BE suggestion, any way to delete and transfer (export) to
the existing db using DAO or ADO?

 

[Tony Toews [MVP]]

Thanks much for the response. I am familiar with the Front End/Back End
solution, but my customer prefers working with a single file (I offered the
FE/BE solution).

Fire the customer. They are wrong.

I have also thought of just sending an "update" .mdb with the updated
queries/forms/reports and just importing their existing tables, but that
would mean they would have to start using the "new" .mdb, adjusting any
shortcuts they've created.

Aside from the FE/BE suggestion, any way to delete and transfer (export) to
the existing db using DAO or ADO?

No idea. I've never done that and I have no intentions of ever
considering that. I'm sure there are means of programmatically doing
that.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[diogenes]

Fire the customer. They are wrong.

I agree they are wrong, but you might want to retrain them instead.

In all my Access apps I have app.mde and data.mdb. Updates are done by
replacing the app.mde. With thousands of users, I've never had one that
couldn't do it.

I'm sure there is a way, but why spend the time?

 

[Rick A.B.]

Craig,

I realize this is not a solution but I would be honest with customer
and tell them that if they want updates and insist on a single file
they will have to stop using the database, send it to you so you can
update it, and wait until they get it back. I can't imagine anyone in
their right mind agreeing to that but there is a cost to not doing
things the correct way.

Rick

 

[Tony Toews [MVP]]

I realize this is not a solution but I would be honest with customer
and tell them that if they want updates and insist on a single file
they will have to stop using the database, send it to you so you can
update it, and wait until they get it back. I can't imagine anyone in
their right mind agreeing to that but there is a cost to not doing
things the correct way.

<smile> Good point. Cause them some incoincidence. That should
help.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/