Hi Mark

I don't remember an EXPORT/IMPORT capability.

CA lets you specify where these things are stored, at least in newer versions. Something like ApplicationData vs Program Files.

There might be references to absolute paths in some files - mostly .ws and .bch, I would think. I would determine where these should be in the new install, then put this stuff in the Emulator\Private directory there and look through for absolute references.

Macros I've made don't usually have any references, but maybe your client does.

Good luck!
Vern

On 12/6/2017 7:55 PM, Mark S Waterbury wrote:
Hi,

I have a client who has an older version of Client Access 32-bit installed under Windows XP ... now they are trying to migrate to a newer version of IBM Client Access under Windows 7 64-bit ...

How can they copy all of their "macros" and configuration files, e.g.:

    .ws    workstation emulator profiles
    .bch    emulator batch files
    .kmp    keyboard maps
    ..pmp    poppad files

etc.  from the old PC to the new PC, so they will "work" with Client Access on that machine?

It seems these files have embedded "path  names" that reflect the old directory structure under e.g. c:\Program  Files and now the Client Access software appears to get installed under "C:\Program files (x86)" and that seems to invalidate those internally stored path names.

Does Client Access provide some kind of EXPORT and IMPORT capability or some other method to copy all of these files and at the same time convert any internally stored path names so they will "work" properly on the  new system?

Please advise.

Thanks in advance.

Mark  S. Waterbury



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.