Re: cannot create design master


"> > Replication manager installed - now there's a difference to my
> > test scenario, it is installed on the development machine, hmm. I
> > also think I'm suffering some serious DLL hell. Finally got it to
> > create a DM on a test machine BUT only after actually installing
> > the DLL's and registering them in the original folders that MS
> > installed them in. Still have to control the whole thing remotely
> > which is also a pain and causing some instability as I suspect the
> > control through JRO and TSI is not stable? . . .
>
> I don't know what you mean here. Do you mean you're running a remote
> terminal session (which should be no problem at all), or that you're
> operating on remote files using JRO/TSI running on your local
> machine. If the lattter THIS IS VERY, VERY DANGEROUS -- anything
> like creating a DM has to open the remote file across across the
> wire, and if the wire has narrow bandwidth and is not reliable, you
> could hose the remote file. This is the whole point of indirect
> replication -- to remove the need of opening the whole file across
> the wire. But there is no replacement for the initial process of
> creating the DM -- that *must* happen locally.
>
> > . . . I need to do it
> > remotely as the user is not actually opening the back end table
> > file at all, just working with a UI I create for them. . ..
>
> Sorry, but this makes no sense to me. They not be opening it in the
> Access UI, but if they are using any data in it, they really are
> opening it.
>
> > . . . DAO has some tools but is rather
> > limited so I'm using whatever is available that gets the job done
>
> DAO only supports the basics of direct replication, which means it
> can create a DM, and is the native, preferred method for doing so.
>
> > . . . DAO,
> > ADO, JRO and TSI. Trying to stick to JRO/ADO but finding it far
> > too limiting as I have to work remotely. . . .
>
> I would recommend *not* working remotely, unless you're running a
> terminal session on the other machine. Remote Desktop works with
> WinXP, and VNC can work with other versions of Windows. If the data
> is on a Win2K or Win2K3 server, out of the box those support up to
> two administrative Windows Terminal Server logons.
>
> > . . . I shall keep trying for a while longer, it just
> > seems strange that on some machines it works fine and not others
> > despite registering the activex's and DLL's.
>
> Can't help you on that, unfortunately.
>
> But I'd stop doing anything whatsoever that pulls the entire MDB
> file across the WAN. That is bound to fail sooner or later and leave
> you in a much worse state than you started.
>



No when I say remote Microsoft in it's "wisdom" presumes that the file you
have open in the computer screen in front of you is the one you wish to be
the design master or in fact is a design master you wish to make a replica.
Very good for the programmer but not very good for a user who has to
actually do the work. So if you create a tool that is a database application
program with a more suitable UI designed to pragmatically create a replica
or a design master of a datafile that is another computer file not yet
opened - i.e. using a connection to actually manipulate the database not
using the database itself and it's UI, it seems that things get messy.

Now this is fine until you find that the DLL versions on the users computer
is not the current version used in the development environment OR that they
are using a latter version of the required DLL. NOW we have DLL hell, do you
replace their version or not? Is it the DLL that is the problem or not? I'm
sure you have encountered this issue? The net result is I am finding it hard
to get past first base and actually provide an application database that has
code that will allow a user to create a design master successfully without
actually using Microsoft's UI. Now considering that I have to cater for up
to dozens of independent users/purchasers of the solution who have trouble
even copying a computer file from one computer to another and they need to
able to at least synchronise their table file, it is fast becoming a
nightmare compliments of Microsoft. Forget the wire, this is on their own
computer, never mind internet or network synchronisation (won't even go
there). In any case it seems I have a "too hard" and I think that for the
first time I shall say die and give a miss. Replication appears to be a
"programer/administrator managed only" solution.


.

Relevant Pages

  • Re: DNS Forward lookup problem - now having problems with a period
    ... How did you set the replication scopes in the zone's properties in DNS on ... > each DNS server? ... to the remote 10.0.2.3 server, which runs on cable (we are working on ...
    (microsoft.public.windows.server.dns)
  • Re: Advice Needed: Asynchronous Replication/Mirroring to central o
    ... Looking for a SQL Server replication book? ... field offices return data to the central office so some of this "advanced" ... geographically-dispersed remote locations. ...
    (microsoft.public.sqlserver.replication)
  • Re: Fixing Replication Failures
    ... If we get replication problems as indicated by repadmin /showrepl, ... We have two local DCs both of which replicate with the remote DC. ... caused by numerous issues from DNS misconfigs, ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD over the Internet
    ... with 5-10 people in each of the 'remote' Sites you have many options ... reliability come into play here. ... You could also place a Domain Controller in each 'Site'. ... types of replication: intrasite and intersite. ...
    (microsoft.public.win2000.active_directory)
  • Re: Moving ADAM instances between sites
    ... creating a site and then using a siteLink object to control ... with no replication scheduled between them then you ... replication to) is not a member of any site link. ... instances to have siteLinks with all the remote instances. ...
    (microsoft.public.windows.server.active_directory)