Re: Problem with opening Conflict Resolver using Shell

OK. The following worked;

strShell = Chr(34) & "C:\Program Files\Common Files\Microsoft
Shared\Database Replication\wzcnflct.exe" & Chr(34) & _
" /DatabasePath " & Chr(34) & "C:\Client\BackEnds\AppTables_be.mdb" &
Chr(34) & _
" /Workgroup " & Chr(34) & "C:\Client\BackEnds\App.mdw" & Chr(34) & _
" /Login " & Chr(34) & "admin" & Chr(34) & _
" /Password " & Chr(34) & "pwd" & Chr(34)

Thanks.


David W. Fenton wrote:
rdemyan@xxxxxxxxxxx wrote in
news:1166595712.692762.4010@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

I still can't get it to work, so here is what I have:

strFilePath = SysCmd(acSysCmdAccessDir)

strShell = Chr(34) & "C:\Program Files\Common Files\Microsoft
Shared\Database Replication\wzcnflct.exe" & Chr(34) & _
"/Login " & Chr(34) & "admin" & Chr(34) & _
"/Password " & Chr(34) & "pwd" & Chr(34) & _
"/DatabasePath " & Chr(34) & strFilePath & "msaccess.exe" &
Chr(34) & " " & Chr(34) & "C:\Client\BackEnds\AppTables_be.mde" &
Chr(34) & _
"/Workgroup " & Chr(34) & "C:\Client\BackEnds\App.mdw" & Chr(34)

I'm unclear on where the reference to access goes.

OK, I misinterpreted what you were doing. You don't need
MSAccess.exe in there at all.

"D:\Programs\Common Files\Microsoft Shared\Database
Replication\WZCNFLCT.EXE" /databasepath
"E:\Data\DFAssoc\Access\Replication\wtsData.mdb" /workgroup
"C:\WIN2K\system32\system.mdw" /login admin /password ********

That's a RUN commandline that worked on my machine. I wonder if the
order of commandline arguments makes a difference?

In any event, I also wonder why you're opening an MDE? An MDE
shouldn't be replicated, as MDEs are only front ends (converting to
an MDE has no effect on a tables-only MDB). Are you passing the
front end instead of the back end?

You're string looks correct (with the removal of the Access
executable, of course), so I wonder if it really is the order that
matters.

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

.

Relevant Pages

  • Re: Problem with opening Conflict Resolver using Shell
    ... I'm unclear on where the reference to access goes. ... That's a RUN commandline that worked on my machine. ... I also wonder why you're opening an MDE? ...
    (microsoft.public.access.replication)
  • Re: Opening report in another db
    ... If you install the referenced library database .mde file in the same ... folder as the front-end application .mde, ... that first and complain about the reference. ... front-end copy .mdb to the obscure library .mde, and finally compiling the ...
    (comp.databases.ms-access)
  • Re: creating external references
    ... The easiest way to implement this is with a referenced MDE. ... Then 'compile' it into an MDE and set a reference in your other ... deploy the frontends as MDBs (because an MDB will recompile against the new ... DLL, which means that all class GUIDs remain the same after a rebuild. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Early vs Late Binding - Final Exam
    ... Checking for 'isbroken' at startup is worthless in an mde: ... > I want to reference some word constants such as Word.Range, ... >> If you have heard that developer's recommend late binding, ... > I got into this mess originally because of the broken/missing libraries. ...
    (microsoft.public.access.externaldata)
  • Re: Opening report in another db
    ... Bob Darlington ... distributed Access 2002 mde's. ... The problem was finding the path to the reference when installed on ... If you install the referenced library database .mde file in the same ...
    (comp.databases.ms-access)