Design Master in Access 2007

[Vicente Marti]

When i open a database, who is a design master of a replica set created in
Access 2003, in Access 2007, and i ask in VBA for DesignMasterID i get a
NULL, but if i open in Access 2003 no problem, if i try to make a replica
from VBA Access 2007 said me that this operation is not permitted for thin
kind of object, someone can help me please?

 

[ruralguy via AccessMonster.com]

I wonder if it because Replication is no longer supported by Access 2007?

 

[Vicente Marti]

Replication is no longer supported by Access 2007, but properties from DAO
Objects related from replication are still available and i can make replicas
and sinchronize then from then menu bar from ui of Access 2007.

 

[David W. Fenton]

I wonder if it because Replication is no longer supported by
Access 2007?

No, that's not it. Replication IS supported by Access 2007, as long
as you use MDB format.

If the file were ACCDB format, I don't know what a request for the
ReplicaID property would return. For non-replicated MDBs, it returns
a zero-length string (not a Null), but I'd kind of expect that the
property wouldn't exist for an ACCDB at all, and would raise the
"property not found" error. I guess it's conceivable that a formerly
replicated MDB could be converted to ACCDB and still retain the
ReplicaID property, but I don't know if it would be a ZLS or the
former ReplicaID.

In any event, the OP has reported that the file in question returns
a valid GUID in one version of Access and not in A2K7, so I don't
know what the issue is. I don't have full A2K7 so I can't actually
run any tests on this.

 

[David W. Fenton]

When i open a database, who is a design master of a replica set
created in Access 2003, in Access 2007, and i ask in VBA for
DesignMasterID i get a NULL, but if i open in Access 2003 no
problem, if i try to make a replica from VBA Access 2007 said me
that this operation is not permitted for thin kind of object,
someone can help me please?

What about the ReplicaID? Does it also return a Null? And what do
you get in A2K7 for the DesignMasterID in any other replica (rather
then the DM)?

(in my other reply I wrote about the ReplicaID instead of the
DesignMasterID, but everything I said also applies to the
DesignMasterID, too)

 

[Vicente Marti]

The file is MDB format, the ReplicaID is not NULL or "" , is a valid GUI
value, just like if we are working with a replica database, i've tried to
take a replica and convert in master design using the option in the menu bar
from ui of ACC2K7, but the result is the same.

 

[Vicente Marti]

Thank you for everybody, it is solved, i've programmed replication using
objects from JRO library, they run well in Access 2007.

 

[David W. Fenton]

Replication is no longer supported by Access 2007,

Where in the hell do you paople get your information? Yes, of course
replication is still supported in A2K7. You say so yourself:

but properties from DAO
Objects related from replication are still available and i can
make replicas and sinchronize then from then menu bar from ui of
Access 2007.

As long as you continue using MDB format (which is a native file
format for A2K7), you can still use replication.

It's only if you convert to ACCDB that you lose replication, as MS
did not see fit to include it in their new version of the Jet
engine, sadly (and stupidly, in my opinion). They also removed
user-level security, another questionable move on their parts.

 

[David W. Fenton]

The file is MDB format, the ReplicaID is not NULL or "" , is a
valid GUI value, just like if we are working with a replica
database, i've tried to take a replica and convert in master
design using the option in the menu bar from ui of ACC2K7, but the
result is the same.

It may be that you've got some form of corruption in your DM and
need to synch with your other replicas, kill that DM and create a
new one. Corruption is not something that is synchronized, so there
is no danger in passing the corruption on to other replicas.

One question that I'm not sure if you've answered:

Do the replicas also give an empty result for the DesignMasterID
property?

Last of all, is this a split application, with only data tables
being replicated? If not, then that's likely the source of your
problems. You just can't replicate forms/reports/modules/etc.
without risking eventually corrupting your replica set. Jet
replication really only works reliably with data tables (despite
what MS's documentation might lead you to believe).

 

[David W. Fenton]

Thank you for everybody, it is solved, i've programmed replication
using objects from JRO library, they run well in Access 2007.

This is silly. Using JRO is a waste of time when you already have
everything you need in DAO.

Are you saying that DAO in A2K7 didn't read things correctly but JRO
*does*?

One issue is that the original release of A2K7 had a bug in it that
caused the DAO Synchronize command to fail. That was fixed in the
first service pack. Perhaps you've not patched your copy of A2K7 and
you were experiencing some aspect of that original bug.