RMS v2.0 HQ Client issues and suggestion

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

Reply to
Terrible Tom
Loading thread data ...

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

Reply to
CptSoft

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.