JimEagleOne < XXXX@XXXXX.COM > wrote in
Well, first off, I've never replicated a form in my life, in any
version of Access, because I understand how replication works, and
knew from the beginning that there was no reason to ever replicate
anything but tables.
But, to be helpful, I converted an A2K MDB to a replica, and found
that, yes, there is no Replicable property. However, if you import
the replicated form into a non-replicated MDB, it is not replicable
in the new MDB. So, it's pretty simple -- just import all your
non-table objects (including queries) into your new front end MDB,
and you'll be fine.
Access 2K can't do it, either.
And I never knew this, as it's something I'd never encounter, since
I would never even imagine replicating forms, etc.
Well, you change the DM and then synch with the problematic MDB.
That will delete the non-table objects and then maybe the problem
will go away.
Of course, if you can't synch at all, then this particular replica
is hosed from the standpoint of synchronization.
That's an expected eventuality when you replicate non-Jet objects.
It's unfortunate that the MS replication documentation still doesn't
make this fact clear.
David W. Fenton http://www.yqcomputer.com/
usenet at dfenton dot com http://www.yqcomputer.com/