I would like to use SQL Remote Replication over a telephone modem connection
with a FILE type link. The app I am working on is being written in VB and
contains an embedded Sybase DB (i.e. Only the DB and required run time files
are distributed).

The manuals show a tutorial on one PC, which works fine. It also refers to a
simple file transfer mechanism that can be used to exchange files
periodically to effect replication. It doesn't say which files should be
transferred and to what directories?

Does anyone have a specific example on how this can be done?

The modem connection will be only temporary and will be through a Comm type
ActiveX control.

Please mail to abinder@uwsi.com

Thanks!

Alfons

This is best asked on the:
sybase.public.sqlanywhere.replication newsgroup.

We have many, many customers using the FILE link over modem dialup lines.

--
David Fishburn
Sybase
Please only post to the newsgroup

TechWave 2000 July 30 - August 3 /2000
http://www.sybase.com/techwave2000

Sybase Developers Network
http://sdn.sybase.com/sdn/mec/mec_home.stm

"Alfons" <abinder@uwsi.com> wrote in message
news:IDR0cp1x$GA.203@forums.sybase.com...
> I would like to use SQL Remote Replication over a telephone modem
connection
> with a FILE type link. The app I am working on is being written in VB and
> contains an embedded Sybase DB (i.e. Only the DB and required run time
files
> are distributed).
>
> The manuals show a tutorial on one PC, which works fine. It also refers to
a
> simple file transfer mechanism that can be used to exchange files
> periodically to effect replication. It doesn't say which files should be
> transferred and to what directories?
>
> Does anyone have a specific example on how this can be done?
>
> The modem connection will be only temporary and will be through a Comm
type
> ActiveX control.
>
> Please mail to abinder@uwsi.com
>
> Thanks!
>
> Alfons
>
>

If the remote publisher ids are SITEnnnn, and the consolidated
publisher id is CONSOL, and the message file subdirectories (the
"addresses") match the publisher ids, and you use the same
subdirectory structure on the remote PCs and the central server, then
here is the arrangement DBREMOTE will use:

\SITEnnnn\CONSOL.xxx - To Remote Site nnnn - From Consolidated DB
\CONSOL\SITEnnnn.xxx - To Consolidated DB  - From Remote Site nnnn

In other words, DBREMOTE on the consolidated will write CONSOL.xxx
files to \SITEnnnn, and it is up to you to transfer that file to the
same-named directory on the remote PC where DBREMOTE will read it.

DBREMOTE on the remote PC will write SITEnnn.xxx files to \CONSOL,
which you must transfer to the central PC where DBREMOTE will read it.

Many folks use shared directories on the central PC to eliminate the
extra step of file transfer. In this scheme, the remote PC dials in,
connects to a shared drive on the central PC, and then DBREMOTE
running on the remote PC reads/writes directly from/to that drive.

FTP works the same way, except using an FTP server rather than a file
server.

For more information see http://www.bcarter.com/tip078.htm

Breck

On Fri, 26 May 2000 16:29:14 -0500, "Alfons" <abinder@uwsi.com> wrote:

>I would like to use SQL Remote Replication over a telephone modem connection
>with a FILE type link. The app I am working on is being written in VB and
>contains an embedded Sybase DB (i.e. Only the DB and required run time files
>are distributed).
>
>The manuals show a tutorial on one PC, which works fine. It also refers to a
>simple file transfer mechanism that can be used to exchange files
>periodically to effect replication. It doesn't say which files should be
>transferred and to what directories?
>
>Does anyone have a specific example on how this can be done?
>
>The modem connection will be only temporary and will be through a Comm type
>ActiveX control.
>
>Please mail to abinder@uwsi.com
>
>Thanks!
>
>Alfons
>
>

Thanks for the response. You have been extremely helpful.

I wish I could use a shared drive on a RAS connection but unfortunately even
our Consolidated DB end users do not necessarily have servers and many of
them are extremely unsophisticated. We needed a "lowest common denominator"
type of solution so we have gone to a VB Dial-in ActiveX Comm Control
(SaxComm) for the communications and file transfer.

Thanks again.

Alfons

Breck Carter <NOSPAM__bcarter@bcarter.com> wrote in message
news:39326aac.2104993@forums.sybase.com...
> If the remote publisher ids are SITEnnnn, and the consolidated
> publisher id is CONSOL, and the message file subdirectories (the
> "addresses") match the publisher ids, and you use the same
> subdirectory structure on the remote PCs and the central server, then
> here is the arrangement DBREMOTE will use:
>
> \SITEnnnn\CONSOL.xxx - To Remote Site nnnn - From Consolidated DB
> \CONSOL\SITEnnnn.xxx - To Consolidated DB  - From Remote Site nnnn
>
> In other words, DBREMOTE on the consolidated will write CONSOL.xxx
> files to \SITEnnnn, and it is up to you to transfer that file to the
> same-named directory on the remote PC where DBREMOTE will read it.
>
> DBREMOTE on the remote PC will write SITEnnn.xxx files to \CONSOL,
> which you must transfer to the central PC where DBREMOTE will read it.
>
> Many folks use shared directories on the central PC to eliminate the
> extra step of file transfer. In this scheme, the remote PC dials in,
> connects to a shared drive on the central PC, and then DBREMOTE
> running on the remote PC reads/writes directly from/to that drive.
>
> FTP works the same way, except using an FTP server rather than a file
> server.
>
> For more information see http://www.bcarter.com/tip078.htm
>
> Breck
>
> On Fri, 26 May 2000 16:29:14 -0500, "Alfons" <abinder@uwsi.com> wrote:
>
> >I would like to use SQL Remote Replication over a telephone modem
connection
> >with a FILE type link. The app I am working on is being written in VB and
> >contains an embedded Sybase DB (i.e. Only the DB and required run time
files
> >are distributed).
> >
> >The manuals show a tutorial on one PC, which works fine. It also refers
to a
> >simple file transfer mechanism that can be used to exchange files
> >periodically to effect replication. It doesn't say which files should be
> >transferred and to what directories?
> >
> >Does anyone have a specific example on how this can be done?
> >
> >The modem connection will be only temporary and will be through a Comm
type
> >ActiveX control.
> >
> >Please mail to abinder@uwsi.com
> >
> >Thanks!
> >
> >Alfons
> >
> >
>

Internet access (dialup and otherwise) is becoming almost universal,
so you might consider message type FTP as a "lowest common
denominator" instead of FILE... get your ISP to give you some FTP
server space, and use it instead of a file server. The DBREMOTEs
running on the remote PCs (as well as the consolidated) will
read/write directly from/to the FTP server, thus eliminating the file
transfer headaches.

You may find dialing in to your own file server is a security
headache; dialing in to an ISP may be much easier.

Breck

On Thu, 1 Jun 2000 10:37:46 -0500, "Alfons" <abinder@uwsi.com> wrote:

>Thanks for the response. You have been extremely helpful.
>
>I wish I could use a shared drive on a RAS connection but unfortunately even
>our Consolidated DB end users do not necessarily have servers and many of
>them are extremely unsophisticated. We needed a "lowest common denominator"
>type of solution so we have gone to a VB Dial-in ActiveX Comm Control
>(SaxComm) for the communications and file transfer.
>
>Thanks again.
>
>Alfons
>
>Breck Carter <NOSPAM__bcarter@bcarter.com> wrote in message
>news:39326aac.2104993@forums.sybase.com...
>> If the remote publisher ids are SITEnnnn, and the consolidated
>> publisher id is CONSOL, and the message file subdirectories (the
>> "addresses") match the publisher ids, and you use the same
>> subdirectory structure on the remote PCs and the central server, then
>> here is the arrangement DBREMOTE will use:
>>
>> \SITEnnnn\CONSOL.xxx - To Remote Site nnnn - From Consolidated DB
>> \CONSOL\SITEnnnn.xxx - To Consolidated DB  - From Remote Site nnnn
>>
>> In other words, DBREMOTE on the consolidated will write CONSOL.xxx
>> files to \SITEnnnn, and it is up to you to transfer that file to the
>> same-named directory on the remote PC where DBREMOTE will read it.
>>
>> DBREMOTE on the remote PC will write SITEnnn.xxx files to \CONSOL,
>> which you must transfer to the central PC where DBREMOTE will read it.
>>
>> Many folks use shared directories on the central PC to eliminate the
>> extra step of file transfer. In this scheme, the remote PC dials in,
>> connects to a shared drive on the central PC, and then DBREMOTE
>> running on the remote PC reads/writes directly from/to that drive.
>>
>> FTP works the same way, except using an FTP server rather than a file
>> server.
>>
>> For more information see http://www.bcarter.com/tip078.htm
>>
>> Breck
>>
>> On Fri, 26 May 2000 16:29:14 -0500, "Alfons" <abinder@uwsi.com> wrote:
>>
>> >I would like to use SQL Remote Replication over a telephone modem
>connection
>> >with a FILE type link. The app I am working on is being written in VB and
>> >contains an embedded Sybase DB (i.e. Only the DB and required run time
>files
>> >are distributed).
>> >
>> >The manuals show a tutorial on one PC, which works fine. It also refers
>to a
>> >simple file transfer mechanism that can be used to exchange files
>> >periodically to effect replication. It doesn't say which files should be
>> >transferred and to what directories?
>> >
>> >Does anyone have a specific example on how this can be done?
>> >
>> >The modem connection will be only temporary and will be through a Comm
>type
>> >ActiveX control.
>> >
>> >Please mail to abinder@uwsi.com
>> >
>> >Thanks!
>> >
>> >Alfons
>> >
>> >
>>
>
>