Excel object cannot fully release after sort

Excel object cannot fully release after sort

Anonymous
Not applicable
234 Views
4 Replies
Message 1 of 5

Excel object cannot fully release after sort

Anonymous
Not applicable
Hi,

I posted this before but the codes still cannot perform well.

Attached lisp is part of my project with combination of vlisp & vba.

The problem is, after calling sort method (mx-sort as in the codes), the
excel object is not able to release. (Can locate on the list of Processes in
Windows Task Manager)

Did I miss something??

Please help....!
0 Likes
235 Views
4 Replies
Replies (4)
Message 2 of 5

Anonymous
Not applicable
Thus spake Calvin:

>> Attached lisp is part of my project with combination of vlisp & vba.

Try the customization group instead. BTW, if you're already using VBA
why not interface with Excel through VBA? It'll require less code.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
0 Likes
Message 3 of 5

Anonymous
Not applicable
Frank:
I am new guy..., only few months in lisp, now trying to VBA... need time!
But this routine can't wait for that.
About your reply, there is no attachement.
Please help..

"Frank Oquendo" wrote in message
news:B0945BE1FE0EE512312A0A8B3EE34D15@in.WebX.maYIadrTaRb...
> Thus spake Calvin:
>
> >> Attached lisp is part of my project with combination of vlisp & vba.
>
> Try the customization group instead. BTW, if you're already using VBA
> why not interface with Excel through VBA? It'll require less code.
>
> --
> There are 10 kinds of people. Those who understand binary and those who
> don't.
>
> http://code.acadx.com
>
>
0 Likes
Message 4 of 5

Anonymous
Not applicable
The attachment you are referring to is your's, Frank was quoting you.

Excel has a problem with its com interface that requires you to release
objects in the reverse order that you created them. I don't have time to
check your lisp, but you should have the lisp ng check it over. You didn't
show any vba code, but its possible that you have some vba code setting a
variable to an Excel object and are not releasing it.

--
--
Ed
--
"Calvin" wrote in message
news:396D6D61AAAD9EF26286E5677FA6FCD3@in.WebX.maYIadrTaRb...
> Frank:
> I am new guy..., only few months in lisp, now trying to VBA... need time!
> But this routine can't wait for that.
> About your reply, there is no attachement.
> Please help..
>
> "Frank Oquendo" wrote in message
> news:B0945BE1FE0EE512312A0A8B3EE34D15@in.WebX.maYIadrTaRb...
> > Thus spake Calvin:
> >
> > >> Attached lisp is part of my project with combination of vlisp & vba.
> >
> > Try the customization group instead. BTW, if you're already using VBA
> > why not interface with Excel through VBA? It'll require less code.
> >
> > --
> > There are 10 kinds of people. Those who understand binary and those who
> > don't.
> >
> > http://code.acadx.com
> >
> >
>
>
0 Likes
Message 5 of 5

Anonymous
Not applicable
Ed,

For those objects created with the code is released without any problem. For
example, if I skip the sort routine, run the active cell selection and
getting the range; all the objects especially Excel object is released
without any problem.
I didn't create any object to perform the sort method. That is the main key,
and I believe I miss something there.

Calvin


"Ed Jobe" wrote in message
news:769333420E5C16CBA9808B35197F51FC@in.WebX.maYIadrTaRb...
> The attachment you are referring to is your's, Frank was quoting you.
>
> Excel has a problem with its com interface that requires you to release
> objects in the reverse order that you created them. I don't have time to
> check your lisp, but you should have the lisp ng check it over. You didn't
> show any vba code, but its possible that you have some vba code setting a
> variable to an Excel object and are not releasing it.
>
> --
> --
> Ed
> --
0 Likes