Run-Time Error 2501

[Ken Snell [MVP]]

I have not worked with ACCESS 2003 (still using 2002), so I can not speak
about its implementation of TransferDatabase.

However, may I suggest that you explore splitting the databases of your
users into front and back ends? You'll save yourself a heap of trouble and
aggravation that will more than pay for the small effort it will take to do
this. Then you can just give the user a new front end whenever necessary,
while the data remain the same in the back end.

See these articles for more info about splitting a database:

http://www.granite.ab.ca/access/splitapp/index.htm

http://www.allenbrowne.com/ser-01.html
--

Ken Snell
<MS ACCESS MVP>

 

[Vikas Bhatia]

I had a similar situation today.

I have several copies of similar databases (not split) on the file server
and I want to keep a master database on my personal drive. I made a table
containing paths to all copies of databases and I was trying to make an
UPDATER tool within Master Database, where I can simply push the updated
Forms/Reports designs to selected databases.

Had same errors:
2501 'CopyObject action was canceled' - when used CopyObject
2501 'TransferDatabase action was canceled' - when used TransferDatabase

Finally I tried to make a completely separate database (Updater.MDB) and
used the same code and it worked.

Give it a try...