how to convert ms access 97 database to access 2003 database

G

Guest

i tried to convert my a97 db to a2k3 db but it gave me an error saying that
"base rowlineage" field doesn't exist in "Msys Tombstone".i needs
clarification on this.
 
G

Guest

Hi Abhi - happy new year

I've never seen this particular error before.
However, the "msys tombstone" may well be teh cause.
Firstly, table names starting "msys" are microsoft "owned" system tables.
This means that the contents may change from version to version - hence we
shouldn't play with them.

I have a feeling that this is not a system table (it certainly isn't a
Microsoft one), and that you have created a table called "tombstone" and
prefixed it with "msys".

Access thinks that this is a system table and is generating your error.

Try changing the table name (remember to change the dependacies too
(queries, macros, code etc).
If this is a big job, you can use a renaming tool like www.speedferrett.com
There's also one at www.rickworld.com too
 
D

Dirk Goldgar

DataMouse.biz said:
Hi Abhi - happy new year

I've never seen this particular error before.
However, the "msys tombstone" may well be teh cause.
Firstly, table names starting "msys" are microsoft "owned" system
tables. This means that the contents may change from version to
version - hence we shouldn't play with them.

I have a feeling that this is not a system table (it certainly isn't a
Microsoft one), and that you have created a table called "tombstone"
and prefixed it with "msys".

No, it's a Microsoft system table that is added when you replicate a
database.
 
J

John Vinson

i tried to convert my a97 db to a2k3 db but it gave me an error saying that
"base rowlineage" field doesn't exist in "Msys Tombstone".i needs
clarification on this.

As noted downthread, MSysTombstone is a table having to do with
database Replication. I have not tried upgrading a *replicated*
database from A97 to A2003 so I don't know if this is a bug in the
upgrader, or what.

I would suggest - for starters - going through the not-inconsiderable
chore of Unreplicating your database; upgrade the result; and (if
needed) replicate the 2003 database.

If that's impractical you might try creating a new, empty 2003
database; use File... Get External Data... Import to import all tye
(non-system) tables; and replicate *that*.

John W. Vinson[MVP]
 
T

Tony Toews

John Vinson said:
and replicate *that*.

Assuming that the original poster even meant to replicate the database
in the first place.

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
 
G

Guest

migration is still pending
i tried to replicate the data but to no use.
needs more clarification on this
 
G

Guest

migration is still pending
i tried to replicate the data but to no use.
needs more clarification on this
 
T

TC

Was the database repliced /before/ you tried to convert it?

If so, you might try asking in microsoft.public.access.replication.
Replication is quite a complex topic. The folks in that group probably
know more about it than we do here.

HTH,
TC
 
T

Tony Toews

Abhi said:
migration is still pending
i tried to replicate the data but to no use.
needs more clarification on this

My point was that it was rather unlikely that you wanted replication
on in the first place.

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
 
T

TC

I'm not clear whether he /knew/ it was replicated, or whether he
misread our comments & has tried to do that again!

TC
 
G

Guest

Thanks for the help...
i tried replicating and now it shows access 2000 file format...
now will try to migrate to a2k3...
i think it shouldn't be that difficult.
 
J

John Vinson

Thanks for the help...
i tried replicating and now it shows access 2000 file format...
now will try to migrate to a2k3...
i think it shouldn't be that difficult.

Abhi, please reread the thread.

NOBODY suggested that you should Replicate the database.

What was suggested is that the table generating the error message WAS
CREATED when you or someone replicated the database, BEFORE you tried
to convert it.


John W. Vinson[MVP]
 
G

Guest

John,

i think i have gone the wrong way.
i have moved to a2k3 from a97
but i finds that some tables are missing
i am looking into the matter.
but couldn't find the reason why.
 
J

John Vinson

John,

i think i have gone the wrong way.
i have moved to a2k3 from a97
but i finds that some tables are missing
i am looking into the matter.
but couldn't find the reason why.

It is quite possible that the upgrading wizard is unable to handle a
replicated database; as I recall, the Replication system tables
changed between A97 and A200x.

It may be necessary to Unreplicate the A97 database (a difficult task
unfortunately), and upgrade that; or to create a new, empty A2003
database and use File... Get External Data... Import to import just
the data tables (not the system tables) from the A97 database.

John W. Vinson[MVP]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top