Author Topic: Active X error message when loading Layer Creator  (Read 1566 times)

0 Members and 1 Guest are viewing this topic.

caddcop

  • Guest
Active X error message when loading Layer Creator
« on: May 21, 2012, 05:51:50 PM »
I have a new user and when I tried to demo the Layer Creator for him, it reported an Active X error. Does anyone know how to correct this?

CAB

  • Global Moderator
  • Seagull
  • Posts: 10401
Re: Active X error message when loading Layer Creator
« Reply #1 on: May 21, 2012, 08:22:57 PM »
What Routine are you using?
Who is the author?
What version are you running?
I've reached the age where the happy hour is a nap. (°¿°)
Windows 10 core i7 4790k 4Ghz 32GB GTX 970
Please support this web site.

caddcop

  • Guest
Re: Active X error message when loading Layer Creator
« Reply #2 on: May 22, 2012, 01:05:13 PM »
Tim Spangler is the author. They are running in 2008 LD. The message appears when the lisp is loaded, right after it prints "Type LC to activate."
As far as I know, it is only on one PC this is occurring.
Also, as far as I know, it is his latest version:
       LayerCreator.lsp v1.9.7
       Copyright© January 2010
       Timothy G. Spangler

TimSpangler

  • Water Moccasin
  • Posts: 2010
  • CAD Naked!!
Re: Active X error message when loading Layer Creator
« Reply #3 on: May 22, 2012, 01:09:30 PM »
What is the error message?  Is the Layer Files folder in the search path?
ACA 2015 - Windows 7 Pro
All Comments and Content by TimSpangler, Copyright © 2016

caddcop

  • Guest
Re: Active X error message when loading Layer Creator
« Reply #4 on: May 23, 2012, 12:40:21 PM »
I will have to check.
I was pretty sure our default profile routine sets up everyone in a uniform manner and then loads their version of our default profile. As I mentioned, this is the first time I have seen the program fail since I started using it regularly.
We ended up using the layer translator since the task at hand was more appropriate for it than simply importing certain layers.
Update: The user had no plot tables defined. once defined (actually, the users File Paths revised to our company standard) the error went away.
« Last Edit: February 14, 2014, 02:52:40 PM by caddcop »