>1) It can’t find the support library where InstallShield puts it (…shared\vfp). But if I then manually copy the DLL files from there to the app’s folder, it works.

>2) But even then it does NOT work for one particular user. When that user logs in and runs the app they get “Fatal error: Exception code=C0000005…VFP8R…”. I’ve uninstalled and reinstalled while logged in as the admin and while logged in as the user. The “problem” user has the same security settings as all the other non-admin users, including both the LAN and the local domain. These are W2K machines with roaming profiles, and, yes, the problem also “roams” with the user. Some of my initial (non-InstallShield) experiments were conducted while logged in as this user, FWIW.
>
>Any ideas?

Win2K was/is kind of an odd hybrid between NT and XP, so it has odd results sometimes, at least for me. AD can either help a lot or cause mysterious problems, also, with NT/Win2K. You might test the same install-setup under XP Pro and see if it works better, if you can...

I had to copy the files like you for NT4 for vfp8, and some Win2K machines - I think it was before we figured out how to configure AD well that I had to do the copying for Win2K. So, that's nothing new - but the problem has never appeared under XP, anyway.

For #2, I would copy the "bad-roamer" somewhere and try a fresh profile for that user, if you haven't yet. It sounds like that may fix the problem, though at the expense of the settings stored in the old profile. I'd say "worth a troubleshot," though, at least to help isolate the problem.