>>>I'm getting an intermittent error when running my exe.
>>>
>>>error 1738
>>>property _icA_Logon is not a method or event
>>>myCont.INIT
>>>Line 31
>>>
>>>The problem:
>>>_icA_Logon is not even referenced in myCont.INIT().
>>>myCont.Init.Line 31:
>>>THIS._acAction = THIS._icA_Open
>>>
>>>_acAction has an assign method attached to it that has _icA_Logon referenced in it, but it isn't getting into _acAction_Assign()
>>>
>>>Line 31 is executed EVERY time the container is INIT(), but it only occasionally crashes.
>>>
>>>Both _icA_Open and _icA_Logon are defined in myCont as Character with values entered into the properties window.
>>
>>
>>Might there be any BINDEVENTS assigned to the _acAction property? BINDEVENTS are difficult to hunt down if you don't know about them.
>>
>>Just a thought.
>>
>>Good hunting!
>>
>>Steve
>
>I'm in VFP 7.0 SP1, so don't have BINDEVENTS.
>Any other ideas?

Another thought would be to play with the timing of things (i.e., slow stuff down in a couple places just to see if it makes a difference by putting a wait(.001) or some such command just in front of line 31 - in the assign? - etc...) It might be that putting this in the Init is problematic due to some built in 'BINDEVENT' type activities going on - something very low level - that does happen even in VFP 7.

I recall a bug in low level timing that Microsoft introduced when they went from 5 to 7 having to do with timing. We had an accounting package that got very flaky on some of our clients systems but not all. And it mostly seemed random. The accounting firm worked with Microsoft for 2 or 3 months, gave up on that when Microsoft couldn't actually solve the problem even though they did find the timing error, and then the accounting firm redesigned their base forms to not do much of anything in the init (as best I recall - might not have been the init as such but it was form timing interference between methods during init/activation of forms - and it was apparently random).

Hope you find a solution,

Steve