RE: Client Access & Rumba co-existence

["Shaw, David" <dshaw@xxxxxxxxxxx>]

Dan,

My previous employer has two NT servers that run Rumba and Client Access
simultaneously to the same AS/400.  We never had any problems with them that
could be attributed to a conflict between the two applications.  The reason
is that they're running DCSI's bar code package (I forget the product name -
Data Collection Advantage or something like that), which needs Rumba to feed
transactions to the MAPICS PM&C interface.  The version of Rumba that we got
had a problem downloading data from the MAPICS file library because there
were too many objects in it, so we had to use Client Access to get to that
data.  It was annoying to have to do it that way (Wall Data wasn't real
supportive about it), but it worked fine.  Just make sure you don't have
client-side name conflicts between the two and you should be okay.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Bale, Dan [mailto:DBale@lear.com]
 
> 
> Since I started here about one month ago in a multi-AS/400 
> environment, I've
> been using Rumba version 6.0 on an NT 4.0 workstation and I 
> hate it.  I have
> asked if I could get Client Access installed and was told 
> that there are
> problems with Rumba and Client Access co-existing.  The source of this
> information was unable to be more specific than that.  Does 
> anyone have any
> experience with this?
> 
> I don't want to cause problems where I have to be "rescued" 
> or where I'd
> have to spend more than 30 minutes recovering from problems.  
> If I knew that
> there would be no problems using CA in this environment, I 
> would gladly
> uninstall Rumba before installing CA.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---