Re: How to copy Design Master as a Design Master.
From: Cheval (NoSpam.Ask_at_ForEmail.com)
Date: 02/15/05
- Next message: Cheval: "Re: MSysCompactError"
- Previous message: David C: "MSysCompactError"
- In reply to: Ritesh: "Re: How to copy Design Master as a Design Master."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 15 Feb 2005 22:11:24 GMT
Ritesh, You're missing the point still. You don't *need* to use a design
master to for those things a replica is perfectly good and actually
preferable.
Different replica GUID? Yes, MS Access was designed that way to do that on
purpose. It would be a very bad thing to have two identical design masters
in a replica set making changes, wouldn't it?
I'm curious, what is the bug that the customer is getting? Maybe you'll
looking for the solution in the wrong place?
Yes, I agree, remove or severely limit the users interaction with the
replica backends. Though I will stress this one final time, the design
master is for the designer/developer, not for users use. What you do with
the information is now your choice.
Glad to be of help. :)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
"Ritesh" <ritesh@hotmail.com> wrote in message
news:%23JD6sj1EFHA.2232@TK2MSFTNGP14.phx.gbl...
Dear Cheval,
Thank you for your reply. What u have said is true, and I understand that
Design Master is for being Design Master only, but application uses the
Design Master for viewing records, entering some administrative information
like active for x days etc..... + some statistical reporting etc.
But regarding the off-site issue, I don't need to replicate the database
back into the customer's on-site database. That's not accepted almost in any
part of the world.
But, my application stops recognizing the Design Master database that I have
copied to off-site. Due to different GUID in replicaid and design master id
properties. Thats the problem. Due to which I was not able to reproduce the
bug that customer was getting.
Anyways, but in MS Access there is a facility to convert replica into design
master / repair Design Master this is one solution to my problem but, I need
to handle the same from application and decrease user interaction with MS
Access directly.
Thanks Chavel once again.
Regards,
Ritesh.
"Cheval" <NoSpam.Ask@ForEmail.com> wrote in message
news:EoQNd.151487$K7.30738@news-server.bigpond.net.au...
> The answer is that you're not understanding MS Access Replication.
>
> Stop the users from using the design master as a backend database. It's
> purpose is solely that of being a "design" master, which is why Access
> Replication creates a replica from the source non-replicated database in
the
> beginning. Research "replica farms" for more information on that.
>
> The bottom line is that in Access, a replica is a design master is a
> replica. Layman's terms; any replica in a replica set can be turned into a
> design master (just remember to delete the current design master first),
so
> you don't need a design master to see the problems.
>
> Therefore, to diagnose the really weird problems that need an external
> off-site environment (eg. database corruptions from poor network or nic
> card, etc), I simply take a file copy of the customers problem replica and
> place in on my machine to do the testing. I can do this because I _never_
> want to replicate it's data back to their replica set.
>
> You don't need to turn a replica into a design master, as it makes no
> difference in doing so.
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> "Ritesh" <ritesh@hotmail.com> wrote in message
> news:%23SJmrFQDFHA.2032@tk2msftngp13.phx.gbl...
> Hi! All there,
>
> I have a problem while supporting people having design master. I am
working
> on an application which is not using replication manager.
>
> A normal MS Access 2000 file is converted to Design Master using JRO.
>
> But, sometimes user gets error on their site. At that time I need to get
> their DesignMaster copied to my support machine for diagnose purpose. At
> that time MS Access & JRO both doesn't recognize it as design master.
>
> Due to this reasone I am not able to reproduce the bug user is getting.
> Hence, unable to support users.
>
> Any solution to this? How to safely copy DesignMaster so that its status
of
> "Design Master" remain as it is?
>
>
> Ritesh.
> ritesh@saltriver.com
>
>
>
- Next message: Cheval: "Re: MSysCompactError"
- Previous message: David C: "MSysCompactError"
- In reply to: Ritesh: "Re: How to copy Design Master as a Design Master."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
