|
We're running Iseries Access 5.7 on the PC, and of course the Iseries Access for Windows Remote Command service is up and running, and apparently works, given the fact that the Access.mdb seems to function, albeit somewhat invisibly. ---- In the 'Iseries Access for Windows Remote Command' service properties, is the box labeled 'Allow service to interact with desktop' (or something close to that) enabled? The symptoms you describe sound like it isn't. Also, under win2k3, default security settings are tighter than earllier versions, so if your program (innocently or not) is dependant on certain environmental conditions (cached server logins, access to particular shares/hosts, etc) to run, you might have to change the user profile the service runs under to get it to work.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.