[AccessD] Destroying form object causes Access 2013 to crash?

[Ryan Wehler]

On initialize they "nothing" themselves but there are no close or destroy/deactivate events for clsTxt and clsCbo unless I copied the wrong code. I got them right out of the archives Brian linked me to yesterday. 

Sent from my iPhone

> On Jan 7, 2017, at 6:19 PM, John Colby <jwcolby at gmail.com> wrote:
> 
> Eachieve class should set the object it is wrapping to nothing.  I usually
> do that in the class'  built in close (unload?) event.
> 
>> On Jan 7, 2017 15:30, "Ryan W" <wrwehler at gmail.com> wrote:
>> 
>> I revise my statement.  It seems to be something in the Control Scanner
>> (or the Text or Cbo Class) doing it.  If I comment out the entire control
>> scanner I can close the form crash free.
>> 
>> I just copy and pasted those classes from John’s posts and everything
>> compiles okay.. Not sure what changed as the classes ‘work’ when in the
>> form but something about the scanner or the class instantiation causes the
>> crash on close.
>> 
>> One thing I do notice is that the clsTxt and clsCbo classes do not ever
>> empty (‘nothing’) the objects.  I assume (probably wrongfully?) that when
>> you set mfrm = nothing it also destroys the class objects that it created?
>> 
>> 
>> 
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com