I tried sending a reply to this thread yesterday - but, strangely - it shows as Sent on my work PC, but, it didn't show up here - nor when I looked at my e-mail at home! So...
This issue was discussed in a meeting today - and now instead of my programming this in VFP - it looks like they want to create some kind of Batch file that they will run to change the Registry settings on a Users machine. Then, our systems administrator person here will take care of getting this implemented. And, like you said Ted - and they brought it up in the meeting - that the batch file must be applied to every new PC or for every new user for this Dept. that requested this fix. I took your advice Ted, from your original reply. I confirmed the Error happens on my PC here at work. So, I saved out the Reg for MS Office - before and After I changed that Trust setting - and found the Reg Key that was changed. However, as you also mentioned below - about your feeling uneasy about changing a security setting. My manager here is also VERY Wary about having this security setting changed. She thinks I should do some research on the impact of changing this setting before we implement it. Just FYI... -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted Roche Sent: Monday, June 01, 2015 3:05 PM To: [email protected] Subject: Re: [NF] Excel Automation - its a Trust Issue... On Mon, Jun 1, 2015 at 2:49 PM, Kurt Wendt <[email protected]> wrote: > OK - Ted, I get your point. Sure was a Zinger of a Delivery. Too much coffee on a Monday morning. Apologies if it came across harshly. > And, yes - understood - not a good idea to leave the solution in the hands of > Users. > > I found the Sample screen - regfile.scx - which I believe is the one you are > referring to. And, as such - to implement this Registry update - such that it > runs (if needed) before the Excel file is generated - and that should do the > trick. There are many resources for reading/writing Registry entries from FoxPro , including a Foundation Class I use often. It's definitely worth doing, as you don't want end-users editing the Registry haphazardly. But I'd be interested if you run into any issues, as a security feature that can be overwritten by an end user doesn't seem all that secure to me. > > Thanks, > -K- > > -----Original Message----- > From: ProfoxTech [mailto:[email protected]] On Behalf Of > Ted Roche > Sent: Monday, June 01, 2015 1:38 PM > To: [email protected] > Subject: Re: [NF] Excel Automation - its a Trust Issue... > > On Mon, Jun 1, 2015 at 12:22 PM, Kurt Wendt <[email protected]> wrote: >> >> Thanks for getting back to me on this issue. As for changing registry >> settings - the problem is that it would be required to do on multiple >> people's computers to make it work. And, that sounds to be a bit of a hassle. > > There's a group of people who specialize in doing just this. They use > something called "programming languages" to write to an "API" that somehow > magically updates registry entries. I dunno how they do it; it's just magic > to me. But perhaps you can find one. They call themselves "software > programmers." > > If they know "FoxPro" you can tell them there are examples in the "Solution > Samples" under "Windows API" They'll know what that means. > >> Almost sounds like it would just be easier to have each user just change the >> Trust settings in MS Office to resolve the issue - as the original QA person >> already did. > > Because users are so much more reliable than programmers. Yeah, that's a good > idea. > > Don't forget to do this for _every_ user that needs to run your app. > And any temps who come in or new employee logins, since it's user-specific. > And any new machines you get in. Or anytime anyone has to reinstall Windows. > >> Anyway - thanks again for your input. > > And thank you for your output. Made my day. > > -- > Ted Roche > Ted Roche & Associates, LLC > http://www.tedroche.com > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4smheyaawpeaqdtp-b9ujdfvtpesskfnhmpravwpfq...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious. Report [OT] Abuse: http://leafe.com/reportAbuse/cacw6n4smheyaawpeaqdtp-b9ujdfvtpesskfnhmpravwpfq...@mail.gmail.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/80838f1ca795b14ea1af48659f35166f1bf...@drexch02.corp.globetax.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
