filePro Error

[Greg Widdows]

Ken,

Yes, it's repeatable. A repeatable scenario is another question. When I 
think the problem is
locked down to a specific report and start working with debug, it works.

What information do you need?

Greg


Kenneth Brody wrote:
> On 7/26/2010 2:31 PM, John Esak wrote:
>   
>> Greg,
>>
>> No, no need for a call... I simply mean that the word Success tells me the
>> programmer (meaning the people who write filePro) had something in the code
>> while they were writing it to help them determine if the lockfile got
>> attended to in some desireable way.  Then, they just forgot to remove this
>> "debugging" code. I could be entirely wrong, but I don't see what else it
>> could be.
>>     
>
> Actually, when you ask the C runtime library "what's the text for error 
> number N" and N is zero, it returns the string "Success".
>
> Now, what caused filePro to see a failure code, yet leave errno set to zero, 
> I couldn't say without seeing at least more information, and preferably a 
> repeatable scenario.
>
> [...]
>   
>>> From: Greg Widdows [mailto:lwiddows at bellsouth.net]
>>>       
> [...]
>   
>>>>> Using Linux, filePro version 5.0.14.
>>>>>
>>>>> Can someone help me out with what the following error might
>>>>> pertain to.
>>>>>
>>>>> *** A System Error Has Occurred ***
>>>>>
>>>>> /u/appl/filepro/invoice/lockfile: Success
>>>>>
>>>>>                          OR
>>>>>
>>>>> *** A System Error Has Occurred ***
>>>>>
>>>>> : Success
>>>>>
>>>>> Thanks in advance.
>>>>>           
>
>