Discussion Locked

use msa2k repl. mngr to synch msa97 dbs?

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a widely distributed app that must run on top of an Access 97 db; it doesn't work if i convert the back end to access2k; since my WAN is too slow to have the remote sites hit the db directly, i'd like to have them run independent copies that then get synched. Trying to use replication manager from office2k developer, it gets all the way through the convert to design master wizard and then tells me "Opertation not supported on replicable databases that have not been converted to the current version."
Is there some way I can get around this?

5 replies

by donq

I wish I had an easy answer for you however I have had my share pf problems upgrading Access 97 "front ends" to work with Access 2k tables.

I know of nothing and would suggest you call (or e-mail) Microsoft Support and if they say no my experience shows 99% of the code converts ok but EVERYTHING must be checked and repaired before redistribution.

Your problem is really in the going back and forth between versions, and whily Access does get better and better Microsoft really doesn't put much effort into version to version compatability. It's more profitable to sell licenses and upgrades!

SORRY

p.s. Everything works super in either version (without converting) linking syncronization code with a field set to Now() in every table.

by rastatech

What you said about the code with a field set to Now(); can you expand on that a little? I've tried using the sync code from the MS page, but it keeps telling me "synchronization is not supported on databases that have not been converted to the current version", even tho it IS the same bloody version. And the sync function for the same replicas works fine from the menu command, but not from code!

by cavedweller

Try exporting the database, then replicating it (for transmission) and importing it into the other version. It might sound like the long way around but a "neutral" data exchange format could solve your versions problem.

This discussion is closed to new replies.