WEB vrs REMOTE

[corey_h...@my-deja.com]

What are some advantages in using the Web Client?
What are some advantages in using the Remtoe Client?
Are Web Client's cheaper?
What is the Web Client? java app, 32bit gui, web page, asp pages?

Do you have a test site I could see?

We are now down to 20 Remote Users. Personally I'm Getting a little
sick of supporting them. I was wanting expert advise on using Web over
Remote.

Thx,

Corey

Sent via Deja.com http://www.deja.com/
Before you buy.

[dan4t...@my-deja.com]

I think the web client you REALLY wnat is the next major version
release... don't know how far out that is.

In article <8nru87$2ct$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

If your remotes are willing to be connected via a remote network (VPN,
RAS, etc), you should run Terminal server on another machine and have
them run a terminal server of citrix client to use SalesLogix.
This is a great solution, especially if you are running Windows2000.
This way you have the power of a workgroup client and the flexibility
of a web client.

I am considering dumb terminals and Terminal Server for all of the
machines at a new building we are connecting.

In article <8o4vpm$i26$1...@nnrp1.deja.com>,

[Matt]

We have been told that when SalesLogix is used with MS SQL Server, thus
connecting through BDE, there are problems using multiple simultaneous
clients on Terminal Server. The explanation mentioned something about
the BDE layer not keeping connections separate when running on the same
Terminal Server.

Are some having success with workgroup clients and MS Terminal Server?

In article <8o5rdv$gbl$1...@nnrp1.deja.com>,

mea...@my-deja.com wrote:
> If your remotes are willing to be connected via a remote network (VPN,
> RAS, etc), you should run Terminal server on another machine and have
> them run a terminal server of citrix client to use SalesLogix.
> This is a great solution, especially if you are running Windows2000.
> This way you have the power of a workgroup client and the flexibility
> of a web client.
>
> I am considering dumb terminals and Terminal Server for all of the
> machines at a new building we are connecting.

[steve_v...@my-deja.com]

We are currently using SalesLogix on a terminal server but only 2 -3
people ever access it at the same time. I haven't noticed any problems
recently. WE did have a locking problem at one point with our
terminal server users

In article <8ogj86$cf1$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

I have yet to experience problems with my remotes using Terminal server.
When running multiple clients, multiple BDE processes as well as
multiple SalesLogix processes open so the pipe opened by each BDE is
unique and should cause no conflicts.

The problem you have described is actually the problem that SalesLogix
experiences when you try to run 2 workgroup clients on the same machine.
The Terminal server kernel fixes this problem.

The only problem I could anticipate with a great number of people
accessing SalesLogix through terminal server is the fact that each time
a new ID is generated, the clients open and modify the SalesLogix.key
file (a relatively poor approach for making unique keys).
Although Terminal server will not allow multiple updates or reads from
the file at the same time, there is a possibility of a slight delay
while one client has the key file open during which another client
would be forced to wait to generate a new ID.

I have not had a problem with this even with 15-20 people connected at
the same time.

The other issue is that since there is only 1 key file, the time it
will take that file to get to 10 million records will be dramatically
shorter.
When the key file reaches 10 million, I am under the assumption that it
will start truncating the number being attached to the key field and
there will be key violations in the database.

Hopefully, Interact will have discovered the identity function in SQL
by then...

In article <8ogqcc$llc$1...@nnrp1.deja.com>,