|
Scott,Thanks; it was the case. I copied and pasted the code from the archives into both the CL program and the body of the email, rather than coping from the CL to the email body. The error message text was just a slip on my part.
Hopefully that's my 'Duh' moment for the week (or at least today). I think I'll go work on my refutation of the Theory of Relativity now.
* Jerry C. Adams *IBM System i5/iSeries Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.995.7024 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Scott Klement wrote:
Jerry Adams wrote:However, it keeps barfing with a Windows dialog box titled "RUNDLL" with the message: "Error in URL Missing entry: FILEPROTOCOL HANDLER".I ran debug over it and the &URL field is initialized.The error message says "FILEPROTOCOL HANDLER", but the actual name of the function is "FileProtocolHandler". There shouldn't be a space in the name. And the name is case-sensitive, so "FILEPROTOCOLHANDLER" is not the same thing as "FileProtocolHandler".Other people have e-mailed this problem to me, and in their case, the problem was a copy/paste problem. They copy/pasted the code, but they had their editor (SEU) configured to only allow uppercase input. This caused the name to get translated from "FileProtocolHandler" to "FILEPROTOCOLHANDLER", causing the problem.I could also see how a copy/paste could end up accidentally inserting a space before the word "HANDLER" as your example shows, that would also make sense.But, the code you posted looks correct. So I'm a little befuddled. Is that actually the code you're using?! How is it being translated to uppercase, then? How is the extra space being inserted between "Protocol" and "Handler"? Something weird is going on...
As an Amazon Associate we earn from qualifying purchases.
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.