CopyObject action cancelled

[DataMiner]

Hi,
My application uses a standard report as a template. Every time the user runs a report, a temporary copy of the standard report is made (using docmd.copyobject) with a unique name. This copy is then modified to that particular users needs. Each day, I have a clean-up function that deletes all those temporary reports.

This worked fine in Access 97. I am in the process of converting to Access 2002, and now find that copyobject fails if there is more than one person using the database. I get error #2501, 'The CopyObject action was canceled."

Yes, I have the database set for shared access.

Any ideas appreciated.

 

[sudhirhinduja]

Hi,
My application uses a standard report as a template. Every time the user runs a report, a temporary copy of the standard report is made (using docmd.copyobject) with a unique name. This copy is then modified to that particular users needs. Each day, I have a clean-up function that deletes all those temporary reports.

This worked fine in Access 97. I am in the process of converting to Access 2002, and now find that copyobject fails if there is more than one person using the database. I get error #2501, 'The CopyObject action was canceled."

Yes, I have the database set for shared access.

Any ideas appreciated.

Hi, did you find a workaround for it?
I'm facing the same problem.
Please assist. Thank you so much.
Suds.

 

[DataMiner]

Yes, split your db front-ends and backends, and give each user their own copy of the front-end.

 

[sudhirhinduja]

FE BE not a feasible solution

Hi,
I cannot do that since its pretty much a dynamic databse in the sense that the primary key in the orders table is mm-dd-yyyy-XX where XX increments based on the next order for the day.
So all have to access the orders table simultaneously and be able to email the order concurrently.
Why does it mess up with multiple users logged in?
Any assistance is greatly appreciated.
Thanks,
Sudhir.

Yes, split your db front-ends and backends, and give each user their own copy of the front-end.

 

[DataMiner]

I don't see why that should keep you from splitting your db into fe and be. The table would be in the backend and simultaneous use by a number of users should not be a problem. I have many very dynamic, very multi-user applications set up this way.

If you don't do this, Access will most likely continue to complain because it does not like you making design changes (ie, creating new reports) in a db unless you have exclusive access. If your reports are in the FE instead, and each user has their own exclusive copy of the FE, you won't have this problem.