I have a database that has been in service for 5+ years now. The
database is stored in Access 2000 file format and is split into a
front end/backend. Users utilize either Access 2007 or 2003 (via a
remote desktop connection) to open the front-end of the database.

Recently, I discovered that I cannot make a copy copy of the two
central data tables to the database. I was trying to make a blank copy
of the database to send to someone. Each time I try to export, import
or copy these tables (in the backend), the following message is
returned:

"Operation is not supported for this type of object". (Access Help
indicates this is an Error 3251.)

I tried copying the linked table from the front end (and pasting
locally) and get the same error message. I was able to make a copy of
the tables without error message using 2003 (over a Remote Desktop
Connection). but that copied table has the same issue (cannot be
copied/exported in 2007). I have done a compact/repair various times.

This seems like an unusual error to me - I've been developing in
access since 1994 and have never seen anything like it.

My main goal is to try to avoid recreating the two tables, as the main
table uses an autonumber as the database id and is linked to 20#
tables via this unique id and I'm worried about maintaining the link
from the main table to the related tables.

Has anyone seen this behavior before? Any suggestions on how to keep
the related data linked up to the main table in the event of a
rebuild?

On Jul 5, 3:45*pm, "Liz O'Donoghue" <lizo.consult... (AT) gmail (DOT) com> wrote:
Did you try a Make Table query from A2K7 with a link to the A2K3
table? Perhaps you can export the table to an Excel spreadsheet, then
import it that way. You can also try looking at the thread:

AutoNumber Regeneration
http://groups.google.com/group/comp....7a4975e6d06a29

where I showed some code that I used to regenerate AutoNumbers before
David Epsom pointed out that an Append Query will honor placing any
unused value into the AutoNumber field. Using an Append Query was
much easier. Post back if I've misunderstood the problem you are
having.

James A. Fortune
CDMAPoster (AT) FortuneJames (DOT) com