RE: User ID in the IM Transactions instead of Workstation ID -- MAPICS-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: User ID in the IM Transactions instead of Workstation ID
From: "Strange, Tim" <TStrange@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 21 May 2002 14:51:47 -0400
List-archive: <http://archive.midrange.com/mapics-l/>
List-help: <mailto:mapics-l-request@midrange.com?subject=help>
List-id: MAPICS ERP System Discussion <mapics-l.midrange.com>
List-post: <mailto:mapics-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/mapics-l>,<mailto:mapics-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/mapics-l>,<mailto:mapics-l-request@midrange.com?subject=unsubscribe>


:-----Original Message-----
:From: Connie Webb [mailto:cwebb@grahamwhite.com]
:Sent: Tuesday, May 21, 2002 2:48 PM
:To: 'mapics-l@midrange.com'
:Subject: RE: User ID in the IM Transactions instead of Workstation ID


:DO NOT name the sessions in Client Access. We tried to identify source of
:transactions this way and brought system to its knees. TCP/IP network and
:MAPICS cannot resolve naming issues for multiple sessions on PC with
:different names.  What to do, still an open issue with us also.

Really?  I run 3 Mapics sessions on my pc with CA using asigned workstation
ID's
IE: MIS12, MIS13, MIS14.  All work well and all of my end users have asigned
workstations ID's.
Our Sales Workstation ID's are Sales1 through Sales25.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: User ID in the IM Transactions instead of Workstation ID , Ted Hendricks

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.