A custumer sent me the following error message:
Subsystem Call: BASE
System Code: 1004
Default Status: .F.
Description: Class: 'NIL' has no exported method
Operation: AITEMS
Arguments:
Involved File:
Dos Error Code: 0
Trace Through:
TMAINFORM:UPDATESTATUSBAR (204)
etc.
Line 204 contains the following code:
::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
It looks like that the Statusbar control is not (properly) installed. Is it
possible that some Windows system DLL's are not installed on his machine??
Regards,
Stephan
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Possible problem with Windows controls
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Stephan,
>A custumer sent me the following error message:
> Subsystem Call: BASE
> System Code: 1004
> Default Status: .F.
> Description: Class: 'NIL' has no exported method
> Operation: AITEMS
> Arguments:
> Involved File:
> Dos Error Code: 0
>
> Trace Through:
> TMAINFORM:UPDATESTATUSBAR (204)
> etc.
>
> Line 204 contains the following code:
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>
> It looks like that the Statusbar control is not (properly) installed. Is
> it possible that some Windows system DLL's are not installed on his
> machine??
If seem that the offending code is executed before the statusbar is created.
Perhaps it's executed on the OnSize event; note that this event is fired
during the form creation on some windows version, while it's fired after
creation on others. Simply check if the statusbar exists before accesing it:
IF ::oStatusBar != Nil
::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
ENDIF
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
>A custumer sent me the following error message:
> Subsystem Call: BASE
> System Code: 1004
> Default Status: .F.
> Description: Class: 'NIL' has no exported method
> Operation: AITEMS
> Arguments:
> Involved File:
> Dos Error Code: 0
>
> Trace Through:
> TMAINFORM:UPDATESTATUSBAR (204)
> etc.
>
> Line 204 contains the following code:
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>
> It looks like that the Statusbar control is not (properly) installed. Is
> it possible that some Windows system DLL's are not installed on his
> machine??
If seem that the offending code is executed before the statusbar is created.
Perhaps it's executed on the OnSize event; note that this event is fired
during the form creation on some windows version, while it's fired after
creation on others. Simply check if the statusbar exists before accesing it:
IF ::oStatusBar != Nil
::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
ENDIF
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Possible problem with Windows controls
Stephan,
>A custumer sent me the following error message:
> Subsystem Call: BASE
> System Code: 1004
> Default Status: .F.
> Description: Class: 'NIL' has no exported method
> Operation: AITEMS
> Arguments:
> Involved File:
> Dos Error Code: 0
>
> Trace Through:
> TMAINFORM:UPDATESTATUSBAR (204)
> etc.
>
> Line 204 contains the following code:
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>
> It looks like that the Statusbar control is not (properly) installed. Is
> it possible that some Windows system DLL's are not installed on his
> machine??
If seem that the offending code is executed before the statusbar is created.
Perhaps it's executed on the OnSize event; note that this event is fired
during the form creation on some windows version, while it's fired after
creation on others. Simply check if the statusbar exists before accesing it:
IF ::oStatusBar != Nil
::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
ENDIF
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
>A custumer sent me the following error message:
> Subsystem Call: BASE
> System Code: 1004
> Default Status: .F.
> Description: Class: 'NIL' has no exported method
> Operation: AITEMS
> Arguments:
> Involved File:
> Dos Error Code: 0
>
> Trace Through:
> TMAINFORM:UPDATESTATUSBAR (204)
> etc.
>
> Line 204 contains the following code:
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>
> It looks like that the Statusbar control is not (properly) installed. Is
> it possible that some Windows system DLL's are not installed on his
> machine??
If seem that the offending code is executed before the statusbar is created.
Perhaps it's executed on the OnSize event; note that this event is fired
during the form creation on some windows version, while it's fired after
creation on others. Simply check if the statusbar exists before accesing it:
IF ::oStatusBar != Nil
::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
ENDIF
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Jose,
it works fine on my computer, but I will give it a try anyway. Thanks for
your advice.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
it works fine on my computer, but I will give it a try anyway. Thanks for
your advice.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Jose,
it works fine on my computer, but I will give it a try anyway. Thanks for
your advice.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
it works fine on my computer, but I will give it a try anyway. Thanks for
your advice.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
And you right, the code is excuted in the FormSize event. Is FormShow a
better place to put such code?
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
better place to put such code?
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
And you right, the code is excuted in the FormSize event. Is FormShow a
better place to put such code?
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
better place to put such code?
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c4424d$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>>A custumer sent me the following error message:
>> Subsystem Call: BASE
>> System Code: 1004
>> Default Status: .F.
>> Description: Class: 'NIL' has no exported method
>> Operation: AITEMS
>> Arguments:
>> Involved File:
>> Dos Error Code: 0
>>
>> Trace Through:
>> TMAINFORM:UPDATESTATUSBAR (204)
>> etc.
>>
>> Line 204 contains the following code:
>> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
>>
>> It looks like that the Statusbar control is not (properly) installed. Is
>> it possible that some Windows system DLL's are not installed on his
>> machine??
>
> If seem that the offending code is executed before the statusbar is
> created. Perhaps it's executed on the OnSize event; note that this event
> is fired during the form creation on some windows version, while it's
> fired after creation on others. Simply check if the statusbar exists
> before accesing it:
>
> IF ::oStatusBar != Nil
> ::oStatusBar:aItems[1]:oControl := ::oLabelCopyRight
> ENDIF
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
Possible problem with Windows controls
Stephan,
> And you right, the code is excuted in the FormSize event. Is FormShow a
> better place to put such code?
Yes, but it's not needed. Just add the check I've told before and it will
work fine, because in that case, the OnSize event is fired several times.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> And you right, the code is excuted in the FormSize event. Is FormShow a
> better place to put such code?
Yes, but it's not needed. Just add the check I've told before and it will
work fine, because in that case, the OnSize event is fired several times.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
Possible problem with Windows controls
Stephan,
> And you right, the code is excuted in the FormSize event. Is FormShow a
> better place to put such code?
Yes, but it's not needed. Just add the check I've told before and it will
work fine, because in that case, the OnSize event is fired several times.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
> And you right, the code is excuted in the FormSize event. Is FormShow a
> better place to put such code?
Yes, but it's not needed. Just add the check I've told before and it will
work fine, because in that case, the OnSize event is fired several times.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Thanks again. I'll let you know.
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Thanks again. I'll let you know.
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Jose,
my customer reports that the problem is gone. So it was indeed the code in
the OnSize() event causing the troubles.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
my customer reports that the problem is gone. So it was indeed the code in
the OnSize() event causing the troubles.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
-
Stephan Hennekens
- Mensajes: 305
- Registrado: Jue Nov 30, 2006 12:17 am
Possible problem with Windows controls
Jose,
my customer reports that the problem is gone. So it was indeed the code in
the OnSize() event causing the troubles.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>
my customer reports that the problem is gone. So it was indeed the code in
the OnSize() event causing the troubles.
Regards,
Stephan
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:46c44520$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Stephan,
>
>> And you right, the code is excuted in the FormSize event. Is FormShow a
>> better place to put such code?
>
> Yes, but it's not needed. Just add the check I've told before and it will
> work fine, because in that case, the OnSize event is fired several times.
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info
>