RMS v2.0 HQ Client issues and suggestion

Posted by Terrible Tom on May 30, 2007, 4:43 pm

Please log in for more thread options

The new license restrictions on HQ Client are bad Bad BAD.

Back in the glorious past known as RMS v1.X, I could install HQ Client on as
many PCs as I wanted. My registers didn't have to rely on another system to
fulfill HQ A/R requests for processing payments or Check Stores requests.

Now, I have HQ Client on one PC per store and the registers rely on that one
PC to handle all requests. If HQ client is busy processing a WS401 and maybe
a WS340 or two and the obligatory WS250s that go along with the WS340s, then
the A/R or Check Stores request times out.

My HQ Clients are constantly needing to e restarted, as they appear to end
up in some sort of endless loop of checking socket or something. The HQ
Client program must be exited and re-launched to resolve the issue.

In addition to the HQ Client issues I'm having, the new PO/Transfer Order
'add items' form is HORRIBLE. Aside from losing the dongle, I'm failing to
see the beauty of RMS v2.0. The dongle was so 1980s it was laughable. Now
I'm not laughing at all--losing the dongle cost me all kinds of positive
functionality.

This is not good. So far, the only thing I like about RMS v2.0 over RMS
v1.3 is the new RMS Dynamics logo. [facetious]When can I expect RMS v3.0? I
expect it to solve all my problems[/facetious]

Tom
--
Stop fishing for e-mail

Posted by Jeff @ Check Point Software on June 7, 2007, 1:43 am

Please log in for more thread options

: quoted-printable

TT,

Restart HQ Client - We are not seeing this issue often. Once a month =
maybe that I'm aware of.

How much RAM are in these HQ Client machines? We try to have at least 1 =
gig with 2 being better.

How often are you connecting nowadays? Most of our clients are once an =
hour with some every 10-20 minutes for 6 - 15 store chains

--=20

Jeff=20
Check Point Software

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D

You must be using Outlook Express/Windows Mail or some other type of =
newsgroup reader to
see and download the file attachment(s). If you are not using a reader, =
follow
the link below to setup Outlook Express. Click on "Open with =
newsreader"
under the MS Retail Management System on the right.

http://tinyurl.com/75bgz
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D

The new license restrictions on HQ Client are bad Bad BAD.

Back in the glorious past known as RMS v1.X, I could install HQ Client =
on as=20
many PCs as I wanted. My registers didn't have to rely on another =
system to=20
fulfill HQ A/R requests for processing payments or Check Stores =
requests.

Now, I have HQ Client on one PC per store and the registers rely on =
that one=20
PC to handle all requests. If HQ client is busy processing a WS401 =
and maybe=20
a WS340 or two and the obligatory WS250s that go along with the =
WS340s, then=20
the A/R or Check Stores request times out.

My HQ Clients are constantly needing to e restarted, as they appear to =
end=20
up in some sort of endless loop of checking socket or something. The =
HQ=20
Client program must be exited and re-launched to resolve the issue.

In addition to the HQ Client issues I'm having, the new PO/Transfer =
Order=20
'add items' form is HORRIBLE. Aside from losing the dongle, I'm =
failing to=20
see the beauty of RMS v2.0. The dongle was so 1980s it was laughable. =
Now=20
I'm not laughing at all--losing the dongle cost me all kinds of =
positive=20
functionality.

This is not good. So far, the only thing I like about RMS v2.0 over =
RMS=20
v1.3 is the new RMS Dynamics logo. [facetious]When can I expect RMS =
v3.0? I=20
expect it to solve all my problems[/facetious]

Tom
--=20
Stop fishing for e-mail
------=_NextPart_000_0225_01C7A88C.24329110
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#008000>TT,</FONT></DIV>
<DIV><FONT color=3D#008000></FONT> </DIV>
<DIV><FONT color=3D#008000>Restart HQ Client - We are not seeing this =
issue often.=20
Once a month maybe that I'm aware of.</FONT></DIV>
<DIV><FONT color=3D#008000></FONT> </DIV>
<DIV><FONT color=3D#008000>How much RAM are in these HQ Client machines? =
We try to=20
have at least 1 gig with 2 being better.</FONT></DIV>
<DIV><FONT color=3D#008000></FONT> </DIV>
<DIV><FONT color=3D#008000>How often are you connecting nowadays?  =
Most of=20
our clients are once an hour with some every 10-20 minutes for 6 - =
15 store=20
chains</FONT></DIV>
<DIV><BR>-- <BR><BR>Jeff <BR>Check Point Software</DIV>
<DIV> </DIV>
<DIV>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D</DIV>
<DIV> </DIV>
<DIV>You must be using Outlook Express/Windows Mail or some other type =
of=20
newsgroup reader to<BR>see and download the file attachment(s).  If =
you are=20
not using a reader, follow<BR>the link below to setup Outlook =
Express. =20
Click on "Open with newsreader"<BR>under the MS Retail Management System =
on the=20
right.</DIV>
<DIV> </DIV>
<DIV><A=20
href=3D"http://tinyurl.com/75bgz">http://tinyurl.com/75bgz</A><BR>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<BR></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #008000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Terrible Tom" <<A=20
=
om</A>>=20
wrote in message <A=20
=
5FCDA-58F7-4C53-9172-645357C91A72@microsoft.com</A>...</DIV>The=20
new license restrictions on HQ Client are bad Bad BAD.<BR><BR>Back in =
the=20
glorious past known as RMS v1.X, I could install HQ Client on as =
<BR>many PCs=20
as I wanted.  My registers didn't have to rely on another system =
to=20
<BR>fulfill HQ A/R requests for processing payments or Check Stores=20
requests.<BR><BR>Now, I have HQ Client on one PC per store and the =
registers=20
rely on that one <BR>PC to handle all requests.  If HQ client is =
busy=20
processing a WS401 and maybe <BR>a WS340 or two and the obligatory =
WS250s that=20
go along with the WS340s, then <BR>the A/R or Check Stores request =
times=20
out.<BR><BR>My HQ Clients are constantly needing to e restarted, as =
they=20
appear to end <BR>up in some sort of endless loop of checking socket =
or=20
something.  The HQ <BR>Client program must be exited and =
re-launched to=20
resolve the issue.<BR><BR>In addition to the HQ Client issues I'm =
having, the=20
new PO/Transfer Order <BR>'add items' form is HORRIBLE.  Aside =
from=20
losing the dongle, I'm failing to <BR>see the beauty of RMS =
v2.0.  The=20
dongle was so 1980s it was laughable.  Now <BR>I'm not laughing =
at=20
all--losing the dongle cost me all kinds of positive=20
<BR>functionality.<BR><BR>This is not good.  So far, the only =
thing I=20
like about RMS v2.0 over RMS <BR>v1.3 is the new RMS Dynamics =
logo. =20
[facetious]When can I expect RMS v3.0?  I <BR>expect it to solve =
all my=20
problems[/facetious]<BR><BR><BR>Tom<BR>-- <BR>Stop fishing for=20
e-mail</BLOCKQUOTE></BODY></HTML>

------=