filePro Error

[Brian K. White]

The system never had 5.6, it had 5.0.15 unintentionally. After hearing 
of the problem the first thing I checked was the version of fp because I 
had a suspicion. Overwriting the existing 5.0.15 bins with 5.0.14 bins 
immediately fixed the problem. No lockfile removal, the box was live the 
whole time.

Unfortunately I can't help with anything like a better description of 
what was actually wrong. Greg had a menu batch that ran about 8 report 
processes in a row and hadn't inserted any implementation to narrow down 
where along the way that that error actually happened and now that it's 
fixed neither do I have any incentive to spend the time tracking down 
yet another 5.0.15 mystery bug for free. This is why it's completely 
unethical to be forcing people to move to 5.0.15, or rather to put so 
many major 5.6 changes into something and still call it a mere 0.0.01 
update AND to put some clear 5.0.14 bug fixes only into 5.0.15 thus 
forcing people to either live with the bug or accept 5.6/5.0.15 problems.

Sorry to rant on an old topic but the pain persists and so the 
complaining persists.

-- 
bkw

On 7/28/2010 2:28 PM, John Esak wrote:
> No problem. Had you mentioned right away that it was a system you moved back
> from 5.15 to 5.14 I would have told you to remove all the lockfiles
> immediately.  That was why my first question asked if you had a system that
> had filePro files which could be touched by both pre 5.6 and post 5.6
> versions.  The lockfiles do not coexist easily.
>
> Glad this helped.
>
> John
>
>
>> -----Original Message-----
>> From: Greg Widdows [mailto:lwiddows at bellsouth.net]
>> Sent: Wednesday, July 28, 2010 11:41 AM
>> To: john at valar.com
>> Subject: Re: filePro Error
>>
>> Thanks again for your help.
>>
>> I appreciate it.
>>
>> Greg
>>
>>
>> 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. You didn't answer the question about two different systems
>>> touching these filePro databases. The older, pre 5.6
>> executables, used a 128
>>> byte lockfile and the post 5.6 use a 512 byte file. So, I
>> was again guessing
>>> that since I've never seen this error in all the time
>> filePro has been
>>> alive... It might be new code that has to do with the new
>> lockfile vs old.
>>> Again, just a guess.  I could not explain it any better
>> than that on the
>>> phone.
>>>
>>> John
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Greg Widdows [mailto:lwiddows at bellsouth.net]
>>>> Sent: Monday, July 26, 2010 10:16 AM
>>>> To: john at valar.com
>>>> Subject: Re: filePro Error
>>>>
>>>> Hi John,
>>>>
>>>> I don't quite follow you on "debugging code that was left in the
>>>> distributed executable by accident"&  " Are you working on
>> a system
>>>> which might allow access to the filePro files by both 5.6 and
>>>> a previous
>>>> version".
>>>>
>>>> Please explain in more detail or if you prefer I could call you.
>>>>
>>>> **NOTE** This menu option runs a series of programs, maybe 5 or 6
>>>> different reports. The error only occurs on 1 PC. In all
>>>> cases, FacetWin
>>>> is used to connect to the Linux server.
>>>>
>>>> Thank you,
>>>>
>>>> Greg
>>>>
>>>>
>>>> John Esak wrote:
>>>>
>>>>> Greg,
>>>>>
>>>>> I can't say what this error refers to, but it sounds like
>> a piece of
>>>>> debugging code that was left in the distributed executable by
>>>>> accident.  Since I've never seen it in decades of using
>> filePro, I'm
>>>>> guessing it is something new in 5.6 that has something to
>>>>>
>>>> do with the
>>>>
>>>>> difference between the old 64 byte lockfile format and the
>>>>>
>>>> new 512 byte
>>>>
>>>>> format. Are you working on a system which might allow
>>>>>
>>>> access to the filePro
>>>>
>>>>> files by both 5.6 and a previous version?
>>>>>
>>>>> But, why would you list this error though, without giving
>>>>>
>>>> some idea of what
>>>>
>>>>> brings it to the screen?  Wouldn't that help us figure it
>>>>>
>>>> out?  Or are you
>>>>
>>>>> asking filePro support directly to look in the source code?
>>>>>
>>>>   You know they
>>>>
>>>>> really have no obligation to read or respond to this forum.
>>>>>
>>>>> John
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: filepro-list-bounces+john=valar.com at lists.celestial.com
>>>>>> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
>>>>>> m] On Behalf Of Greg Widdows
>>>>>> Sent: Friday, July 23, 2010 1:09 PM
>>>>>> To: Filepro_List
>>>>>> Subject: filePro Error
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> Greg
>>>>>> _______________________________________________
>>>>>> Filepro-list mailing list
>>>>>> Filepro-list at lists.celestial.com
>>>>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> Filepro-list mailing list
>>>>> Filepro-list at lists.celestial.com
>>>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>>>
>>>>>
>>>>>
>>>
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>
>>>
>>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>