I remember a prior release of VFP (6 or 8) compiled EXE's would C0000005 on startup due to a bad path. That was always hard to resolve over the phone prior to remote access tools.
-----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted Roche Sent: Wednesday, April 18, 2018 2:33 PM To: [email protected] Subject: Re: "Cannot load 32-bit DDL wwipstuff.dll" On Wed, Apr 18, 2018 at 2:26 PM, Tracy Pearson <[email protected]> wrote: > That specific EXE is now blocked by the local anti-virus solution. > A customer had that problem a few weeks back. I never heard the results after we pointed out a second VFP app worked with the tools in question without a problem. We could not get in to the settings of the A/V to un-ban the EXE, nor could we confirm it had banned the EXE. > Wow, it's like we're programming in a hostile environment! Thanks, all, for your suggestions. Problem seems to have, er, subsided. Looks like a non-existent directory slipped into the path ahead of where the DLL was located, so the search algorithm gave up before finding the DLL. We moved the DLL to the same folder as the EXE and it's working now. -- 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/[email protected] ** 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.
