Help with MSysAccessStorage   

OK, so i have been doing A LOT of reading about this problem. Some of
my users are getting the "Do you want to solve the conflicts" when
they log on to the db. It is showing ALWAYS the same problem
"MSysAccessStorage (8)". So it has 8 conflicts. I always click on keep
winning and everything works great. BUT i just can not understand why
this problem/conflict keep showing up. I have read that this table
(MSysAccessStorage" is part of MS Access 2002, but again I build this
db using MS Access 2003.

Can somebody pleaseee tell me what can I do to solve this problem.
What do I need to change where do I need to look. This conflict
happends everytime. I know I should have split my db to a back/front-
end but i did not because I was not aware of this. Now that more than
30 users have this db on their laptops this option is not a solution.

Thanks in advance

date: Fri, 28 Sep 2007 21:20:27 -0000   author:   erick-flores

Re: Help with MSysAccessStorage   

erick-flores  wrote in
news:1191014427.879659.128270@k79g2000hse.googlegroups.com: 

> OK, so i have been doing A LOT of reading about this problem. Some
> of my users are getting the "Do you want to solve the conflicts"
> when they log on to the db. It is showing ALWAYS the same problem
> "MSysAccessStorage (8)". 

It is obvious that you have a design error in your application if
you have an MSysAccessStorage table in a replicated database. 

Front ends should *never* be replicated, because front ends contain
forms, reports, etc., which are Access objects. Replication is a Jet
technology, and is reliable only with Jet objects (tables and
queries). 

Thus, your front end should *not* be replicated at all. If you
unreplicate your front end (simply create a new MDB and import all
the front end objects and link tables to the replicated MDB; then
delete everything but the tables from your design master). 

> So it has 8 conflicts. I always click on keep
> winning and everything works great. BUT i just can not understand
> why this problem/conflict keep showing up. I have read that this
> table (MSysAccessStorage" is part of MS Access 2002, but again I
> build this db using MS Access 2003.
> 
> Can somebody pleaseee tell me what can I do to solve this problem.

Don't use replication on front end objects, ever.

> What do I need to change where do I need to look. This conflict
> happends everytime. I know I should have split my db to a
> back/front- end but i did not because I was not aware of this. Now
> that more than 30 users have this db on their laptops this option
> is not a solution. 

Replicating the front end (or not splitting the app in the first
place) was a huge implementation error on your part. That said, it's
something the MS documentation implicitly (and completely wrongly)
endorses. 

-- 
David W. Fenton                  http://www.dfenton.com/ 
usenet at dfenton dot com    http://www.dfenton.com/DFA/

date: Fri, 28 Sep 2007 21:06:31 -0500   author:   David W. Fenton lid