My problem is that I have developed a pretty complex database quite a few years ago with access 97, later upgraded to 2000 version. The database includes a fair amount of code, but main issues have come when converting it to a replicated db. This helped solve the problem of synchronisation between various users and ability to use the DB offline when travelling abroad. but replication has caused serious complications which forced me to stop making changes to the structure to avoid continuous damage to the VB project! Converting to a later version is impossible as replication is no longer supported, and therefore I have had to start from scratch with a new db on 2013, hence wanting to have both 2000 and 2013 on the same machine. But as Richard confirmed, it does not work and the continuous reconfiguration I fear could cause damage to this db.
I the end I solved the problem the easy way... By purchasing a new laptop where I have installed the new access version!

---

Reply from Richard Rost:

I used to have nothing but continuous problems with database replication. I ended up building my OWN replication algorithm that manually checked each field for changes. It worked, but it was slow.