Thanks to all that replied.

I have much to think with the suggestions that have been presented.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Sunday, August 23, 2015 9:30 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Which emulator am I running

Seems to me if you plan to deploy different versions of Client Access you could also put the Office Integrator on the relevant desktops as well.

Then you can also identify which versions of Client Access are loaded.

But you've already heard me say that :-)


Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems richard.schoen@xxxxxxxxxxxxxxx Visit me on: Twitter | LinkedIn


message: 3
date: Sat, 22 Aug 2015 14:49:38 +0000
from: Michael Smith <msmith@xxxxxxxxxxxxxx>
subject: RE: Which emulator am I running

We currently have the RJS Office Integrator solution and it is deployed on some but not all of our desktops. There is also no plan to install on all desktops.

There is coding in place has to "shorten" the command string to <123 to overcome not having the RJS Office Integrator... I would like to deploy the ACS(IBM Access Solutions) as the standard desktop and use the 1000+ length that is available with that emulator..... To me , it would really be nice, if I could programmatically determine which emulator... and use the longer command string.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].