Without lisp VB/VBA can not do everything in AC. Lisp can do everything in
AC. Some prime examples are the draworder, and trim command. With VB/VBA you
can not trim, you would need to recalc the points and reassign them to the
object. Lisp can trim entities. Without the sendcommand in vba you would
never be able to change the draworder of entities. VB/VBA can not create AC
commands IE in lisp one could (defun c:junk ()...) and the user could type
junk at the command prompt and execute the command. To do this in VB/VBA one
must first do (defun c:junk () (vl-vbarun "vbaSub")). Only then could the
user type in junk at the command prompt and execute the sub. I learned to
write lisp first (years ago), but enjoy writing vb/vba now. I feel the
writing in vb/vba and using defun's to create command's makes me a better
programmer because I continue to develop my vb/vba skills, which there are
many more places to write vb than lisp.
HTH
Chris
"Andy & Starr"
wrote in message
news:3C3F856D.EF87C9CC@bellsouth.net...
> > Hi all I am looking to see what VBA can do that cannot be done in Lisp
> > or VisualLisp. I know about the dialog box differences already. I am
> > looking for non dialog box functionality.
>
> When the task is manipulating autocad, the two languages have nearly
> identical capabilities. If the task is a routine to operate on autocad
> alone, lisp would probably be the tool of choice for an accomplished
> lisp programer. VBA provides access to any activeX enable program and
> the operating system, making it suitable for a project that interfaces
> with a database or spread sheet. As you mentioned, vba includes rich
> interface capabilities. An important aspect of adesk's inclusion of an
> object model in cad was not just providing the cad user with vba, but
> providing VB programers access to cad.
>
