why does synchronization fail in access 2007

[Guest]

I cannot get access 2007 to synchronize replicas having made changes to the
design master. I have kept the DB in mdb format and have permissions as in
access 2002. The synchronization fails becuase ' either Table '|' is open or
cannot be programmatically manipulated'. It will synchronize if I don't make
chnages to forms or tables. Any ideas? Is this a known issue?

 

[David W. Fenton]

I cannot get access 2007 to synchronize replicas having made
changes to the design master. I have kept the DB in mdb format and
have permissions as in access 2002. The synchronization fails
becuase ' either Table '|' is open or cannot be programmatically
manipulated'. It will synchronize if I don't make chnages to forms
or tables. Any ideas? Is this a known issue?

Have you tried closing the two partner replicas and deleting any LDB
files? Have you compacted twice after the design changes and before
the synch?

And, last of all, and probably most important:

Is your application split into non-replicated front end and
replicated back-end tables?

 

[punjab_tom]

dude use SQL Server for replication; MDB is for babies that are too
****ing stupid to get certified

 

[Guest]

Thanks. Tried compacting each twice, still no luck same message. There is no
split back and front end. LDB - are locked files ? If so there are none in
either folder.
Ian

 

[David W. Fenton]

Tried compacting each twice, still no luck same message. There is
no split back and front end. LDB - are locked files ? If so there
are none in either folder.

The problem is that you aren't split, and you're probably beyond the
point of no return, at least on the Access project end of things
(i.e., your forms/reports/etc.).

Create an unreplicated MDB and import all your forms/etc., then
delete them from the Design Master. At that point, it may be that
data will start synchronizing again, but it may not.

The whole point is that there is no Access app other than the most
trivial single-user app that should not be split.

And when replication is involved, you're obviously in multi-user
mode, so you *must* split. And you have to do it for another reason,
because not doing so will eventually corrupt the whole thing to the
point of complete loss of the Access project (i.e., the
forms/reports/etc.).

 

[punjab_tom]

The whole point is that there is no Access app other than the most
trivial single-user app that should not be ADP.

 

[David W. Fenton]

The whole point is that there is no Access app other than the most
trivial single-user app that should not be ADP.

This is idiotic and just plain WRONG.

An ADP works only with SQL Server, so it's not a relevant choice
when you are using a Jet back end.

 

[punjab_tom]

NOBODY SHOULD USE A JET BACKEND FOR _ANY_ REASON

SQL Server is bigger, better, and the same price

compare SQL Server Management Studio to Access Query By Design /
Example window; ok ****tard?

Lose the training wheels; I've got MS employees that say QUOTE JET HAS
BEEN DEAD FOR SIX YEARS END QUOTE.

STICK A ****ING CORK IN IT KID; MDB IS FOR LAMERS.
MOVE YOUR DATA TO SQL SERVER: THE CAPABILITIES COMPARED TO MDB IT IS
LIKE HEAVEN VS HELL.

I DON"T SPEND ALL MY TIME WRITING DAO LOOPS.
I DON"T SPEND ALL MY TIME BOUNCING FILE SERVERS TO KICK PEOPLE OUT OF
A STUBBORN DATABASE

I DON"T SLAVE AGAINST LOCKING PROBLEMS _MOTHER_FUCKING_EVER_

stick a cork in it dipshit; MDB is for lamers and retards that don't
know SQL well enough to survive



it's RIDICULOUS to expect database newbies to learn 2 different
dialects of SQL

TSQL WINS EVERY COMPARISON

 

[punjab_tom]

The whole point is that there is no Access app other than the most
trivial single-user app that should not be ADP.

 

[David W. Fenton]

Thanks. Tried compacting each twice, still no luck same message.
There is no split back and front end.

That's where you need to start to solve your problems. Jet
Replication is a Jet technology and works reliably only with Jet
objects (tables/queries). And any application should be split by
definition, unless it's being used by a single user (and I don't
even do it in that case), and if it were, then you wouldn't need
replication!

LDB - are locked files ? If so there are none in
either folder.

OK. That eliminates one possible problem.

Until you split your database so that your front end is not
replicated, there's not much more advice I can give.

 

[punjab_tom]

And any application should be ADP by
definition, unless it's being used by a single user (and I don't
even do it in that case), and if it were, then you wouldn't need
Access!