[AccessD] Destroying form object causes Access 2013 to crash?
Ryan Wehler
wrwehler at gmail.com
Sat Jan 7 19:20:36 CST 2017
Correct just your class example. I sent it zipped to your personal email.
Sent from my iPad
> On Jan 7, 2017, at 7:07 PM, John Colby <jwcolby at gmail.com> wrote:
>
> Sure, sent to me offline. I assume that it is just my class example, not your own FE?
>
>> On 1/7/2017 7:04 PM, Ryan Wehler wrote:
>> Do you want the whole accdb?
>>
>> Sent from my iPhone
>>
>>> On Jan 7, 2017, at 6:01 PM, John Colby <jwcolby at gmail.com> wrote:
>>>
>>> I'll look at it tonight. Can you email me your code?
>>>
>>>> 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
>
> --
> John W. Colby
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
More information about the AccessD
mailing list