Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Error Record Out of Range
Message
From
14/08/2018 06:42:06
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01661541
Message ID:
01661579
Views:
52
>>>Hi,
>>>
>>>I have one or two customers where their error log shows an error in a method Start. And the error message is "Record out of range." The customers themselves never reported this error; I just see it in their log file.
>>>
>>>This method Start is of the global application object (oApp) is called at the top of the application.
>>>
>>>The code in the Start method is as follows:
>>>
>>>
>>>PROCEDURE Start
>>>
>>>	do while .T. 
>>>	
>>>		read events
>>>		if this.cleanup()
>>>			on shutdown
>>>			this.cleanup2()
>>>			if type('oPassword') = 'O' .and. !ISNULL( oPassword )
>>>				oPassword.Close_user_login_file()
>>>				oPassword.destroy()  
>>>				oPassword = .NULL.
>>>				release oPassword
>>>			endif
>>>			exit
>>>		endif
>>>
>>>	enddo
>>>
>>>
>>>I don't see any line of the code above that would cause the "record out of range."
>>>
>>>I have two questions:
>>>1. If the error happened in a method called by Start (cleanup() and cleanup2() and method .Close_User_Login_File()), the error should point to that method and not Start(); correct?
>>
>>I wonder if the error occurs in the start-up of a form, specifically in stuff that isn't code and thus wouldn't have a line number. Either in instantiating controls or in assigning property values from the property sheet.
>>
>>Tamar
>
>I don't think there is a form that is being instantiated at the time when error occurs (to your comment about "start-up of a form").
>
>It is possible that the error occurs in one of the methods that are called by Start method. But this is what I am wondering, if the error would then have the name of the method where the error occurred.

If it were in the one of the other methods, that's what you'd see. That's why I suggested it's in code that isn't in a method. Are you capturing the whole call stack in your error log?

Tamar
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform