Delete a report in an external Access database

[RobJ]

I have a database that has been distributed to users. I have a need to replace one of the reports in the distributed database (small bug fix). I would like to send users a small database containing code to delete the old report in their database and replace it with the new report. I have been able to create the code to export the new report but not to first delete the old report.

I have tried using this code:

Dim obj As AccessObject, dbs As Object
Set dbs = Application.CurrentProject
For Each obj In dbs.AllReports
    If obj.Name = "Report1" Then
        DoCmd.DeleteObject acReport, obj.Name
    End If
Next obj

This works perfectly well if dbs is the current database but if dbs is set to an external Access database I get an error message at the line

 For Each obj In dbs.AllReports

.



Any help appreciated.

[June7]

This is not a split db?

I can't find any reference with an example to accomplish this.

[RobJ]

No, not a split database. I want to be able to give users a program to run that will delete the old version of their report and copy a new version. I have created a small database with an Autoexec that will run the code to 1)
Delete the old report and 2) copy the new report to their existing database. I can get step 2) to work but not step 1). The code I tried will work but only on the current project, not on an external project.

[June7]

I understand what you want and cannot find code that will delete a report in another db.

Possibly might have to somehow copy a procedure into users db (maybe Docmd.TransferDatabase). That procedure would have the code to delete report and import new. None of this is anything I've ever tried. However, I do know how to call a procedure in another db.

Are these distributed copies intended to be single-user? Even so, modifying interface would be much simpler if db was split.

[RobJ]

Thanks for you help. I misunderstood about the split db. The distributed app is a split db (front and back-end). I can simply provide an updated front-end db but thought it might be easier to just replace the report. I too could not find a method of achieving this but thanks for your time. Interestingly enough, the method I have tried does work if the object is a table.

[isladogs]

Whenever you want to modify or replace an object or module code in the FE of a split DB, you should always do so by distributing a new version of the FE.
You can also run code from the new FE to modify the design of tables in the BE if necessary. That may be the code you were referring to earlier

[RobJ]

Whenever you want to modify or replace an object or module code in the FE of a split DB, you should always do so by distributing a new version of the FE.
You can also run code from the new FE to modify the design of tables in the BE if necessary. That may be the code you were referring to earlier

Thanks isladogs. You are right, it does make sense to distribute a full, new version. That way you know it works. I'll take your advice.