Re: What is the problem with GetPrivateProfileString?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"Steve Richfie1d" <Steve@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3sr7v3FplhjgU1@xxxxxxxxxxxxxx
>> I'd also use Err.Raise instead of Error since Error is there
>> only for backward compatibility (from the time when MS cared about
>> that sort of thing!)
>
> There ARE some subtle differences that probably would be no problem
> here. There are some undesirable side effects on the Err object from
> some uses of the Err object that don't occur with the Error function
> and statement, which has made some really subtle past bugs in my error
> handler. The safest way seems to be to use Error unless you can't, in
> which case fall back onto Err and hope that the side effects don't
> hurt you.

Can you elaborate and/or provide an example of something that behaves
differently?

--
Reply to the group so all can participate
VB.Net: "Fool me once..."

.