Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Fatal error: Exception code=C0000005 on bindcontrols=.t
Message
De
29/05/2003 15:24:37
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00793062
Message ID:
00794145
Vues:
28
I was told by one of the other team members that this is actually a known issue and is being addressed. Thanks for your help!


>Unfortunatly I can not reproduce the error on demand.
>I tried to use my suspections to write repro code. But without good results.
>All works as it should. I must be missing something important.
>
>My suspections:
>It seems that the problem is related to using editbox controls placed on pageframe pages to edit character type field ( for example C(60) and C(120) ). When I change type of the fields to Memo the problem disappears.
>The problem disappears also when I clear controlsource property of the editbox controls.
>
>Thanks
>
>
>>Hi Jozef,
>>
>>If you can come up with some code that reproduces the error consistently, please post it along with environmental data (OS, localization, etc) here in response to me and I'll be glad to research it.
>>
>>
>>>From time to time I have a problem with Fatal error: Exception code=C0000005
>>>It occours during instantiation of different forms.
>>>Report errors indicates (depending on forms) two lines
>>>thisform.BindControls = .t.
>>>or
>>>this.controlsource = "table.field"
>>>
>>>I can not reproduce the error because most the time the forms are running without problem.
>>>This ugly behavior exist on several computers with win2000 or winXP.
>>>
>>>I have no idea what to do with this. It seems to me that this error is somehow related to editbox controls but I'm not sure.
>>>
>>>I spend several hours looking for solution - without results.
>>>Any idea what to do with such problem ?
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform