There is a couple of ways to look at this.  It sounds like your app is
hitting the network brick wall.  If your network is running slow, then
the performance of your app will be bad.  So may be there are some
things to look at from the network side.

The other point is this.  If you make a habit of access data remotely,
then may be you should use a IPC routing system.  This system is two
programs, with in separate job streams.  One program is the sender of
data requests.  The other program is the receiver of the request and the
sender of the data, per the request. One system will be the sending
system and the other the receiving system.  That is unless both systems
require data from their sister system.  Then there would be a sender and
receiver on both systems.

Keep in mind that when writing apps that access data over networks, the
key unknown is the network.  Unknown, because there is so much that can
effect its performance that may have nothing to do with you.

Ron Horner
Operations Manager
Administrative Management Group
[log in to unmask]


        -----Original Message-----
        From:   Loren Froomin [SMTP:[log in to unmask]]
        Sent:   Thursday, March 18, 1999 5:30 PM
        To:     [log in to unmask]
        Subject:        TurboIMAGE Remote Access

        I am experiencing a performance problem when trying to
        access a TurboIMAGE DB remotely in a program.  I am
        following the Ch.9 section of the TurboIMAGE manual.
        I am using the following commands using the COMMAND
        intrinsic:

        remote hello user/pass.account/pass;dsline=localhost
        file dbname=dbname.group.account:localhost

        open the database
        close the database

        reset dbname
        remote bye


        The code works fine; it just takes too long (several
        seconds).

        Is there a way to optimize this code?  Is there a
        different way to access a TurboIMAGE DB remotely (not
        using a database access file)?

        The database and logon information is specified at
        runtime.  It is also not possible to expect the DB
        to be open for access across accounts.

        Any assistance would be greatly appreciated.

        Regards,

        Loren