Access UNreplicated.
Hi all, trust you are well.
Design master/replica scenario all working great. One of our users Compacted and Repaired their replica and straight after doing that it become "unreplicated". I cant sync now with the design master now as the only option i have is to create this replica as the design master. I need the data in this replica - how do i return it to being replicated?
Thanks
Sean
Design master/replica scenario all working great. One of our users Compacted and Repaired their replica and straight after doing that it become "unreplicated". I cant sync now with the design master now as the only option i have is to create this replica as the design master. I need the data in this replica - how do i return it to being replicated?
Thanks
Sean
ASKER
Nope no backup. The user was about to sync and thought it would be nice to do a quick compact and repair.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So in a nutshell I cant return the file to its "replicated" state by the sounds of things?
That's hard to say, since there's no way for us to know why it's being reported as unreplicated. You could always contact a repair service (like www.pksolutions.com or www.everythingaccess.com) for assistance, but it won't be free.
Depending on how much data has been entered since the last sync, you may be able to manually update another replica and recover the "lost" data. Of course, this can be a hit-or-miss scenario depending on your particular business and how it uses the data.
Depending on how much data has been entered since the last sync, you may be able to manually update another replica and recover the "lost" data. Of course, this can be a hit-or-miss scenario depending on your particular business and how it uses the data.
LSM ... Just wondering, have you ever actually had JetComp 'work', ie ... actually fix anything? I have not. Also ... isn't the 'latest' version of JetComp actually dated pre-A2003?
Thanks ...
SeanNij ... I only have on client using Rep ... and I literally told them: "IF ... you don't do a backup before you do a rep sync ... AND ... you end up with a problem ... THEN ... don't call me, lol (seriously).
mx
Thanks ...
SeanNij ... I only have on client using Rep ... and I literally told them: "IF ... you don't do a backup before you do a rep sync ... AND ... you end up with a problem ... THEN ... don't call me, lol (seriously).
mx
ASKER
Mx, there are a lot of my clients i would like too say other things too when they dont backup but i think it would be cencored by EE....
LSM - Jetcomp did work. Must admit it is one of the rare times when it does in defence of mx...
Thanks for all you help.
LSM - Jetcomp did work. Must admit it is one of the rare times when it does in defence of mx...
Thanks for all you help.
So, JetComp did work?
If so, that is good to know!
mx
If so, that is good to know!
mx
<LSM ... Just wondering, have you ever actually had JetComp 'work', ie ... actually fix anything? I have not. Also ... isn't the 'latest' version of JetComp actually dated pre-A2003?>
Yes, but rarely. Generally if the builtin C&R won't work then JetComp won't either, but I've personally had files that C&R wouldn't fix that JetComp fixed in a hurry. From my understanding, the processes used by JetComp are slightly different than those used by the built ones since JetComp doesn't have to close the current database - it can just immediately perform the C&R.
<isn't the 'latest' version of JetComp actually dated pre-A2003?>
JetComp doesn't really have anything to do with Access versions, as it works on the Jet database engine and has nothing to do with Access itself. It does "work on" Access objects, but that has more to do with the way Access stores those objects than it does with the way JetComp works.
Jet 4.0 has been used since Access 2000, so I doubt any work has been done on it since then.
Yes, but rarely. Generally if the builtin C&R won't work then JetComp won't either, but I've personally had files that C&R wouldn't fix that JetComp fixed in a hurry. From my understanding, the processes used by JetComp are slightly different than those used by the built ones since JetComp doesn't have to close the current database - it can just immediately perform the C&R.
<isn't the 'latest' version of JetComp actually dated pre-A2003?>
JetComp doesn't really have anything to do with Access versions, as it works on the Jet database engine and has nothing to do with Access itself. It does "work on" Access objects, but that has more to do with the way Access stores those objects than it does with the way JetComp works.
Jet 4.0 has been used since Access 2000, so I doubt any work has been done on it since then.
mx