John,

I solved my problem below and am able to get XLC running again..

Was looking at the Bricscad site forum on another issue and ran into this that discussed a similar problem. Short story is it looks like Office 2007 install wrote bad info in the registry that affected Office 2002 (I have both Office 2002 (Office ver 10) and Office 2007 (Office ver 12) applications installed).

The 3rd suggested solution is what I followed. As I am using Windows XP Pro 32 I changed the file path slightly to the VBE6.dll, using 'Program Files' instead of 'Program Fixes (x86)'…see the highlighted below.

From www.bricsys.com/common/knowledge/topic.jsp?id=304

Symptoms
When running a VBA macro the following error pops up:
error: "file not found: vba.6dll"
Cause
This is probably caused by an installation of Office 2010 or another application that installs VBA 7. This installation can cause corruption of a VBA6 registry key, that causes an incorrect reference to the VBA 6 dll's.
Resolution
Possible solutions are suggested on these links :
- blogs.msdn.com/b/developingfordynamicsgp...cket-1474386816.aspx
- www.excelforum.com/excel-programming/666...-found-vba6-dll.html
- If registering VBE6.dll as suggested in the previous link doesn't help, have a look at the value of the following registry key:
"HKEY_CLASSES_ROOTTypeLib{000204EF-0000-0000-C000-000000000046}6.09win32"
Perhaps it points to an unexisting file, e.g. on a 64 bit system : "C:\Windows\SysWOW64\msvbvm60.dll". Then try changing it to "C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA6VBE6.DLL".

(delete the (x86) portion of the path if using a 32 bit OS. Best to confirm path to the VBE6.DLL file.

So my particular circumstance was installing some Office 2007 apps but keeping Excel 2002…this was done after the original XLC install, which remained ok until I upgraded. At that point the XLC install could not find the VBE6.dll as the registry was changed by Office 2007.

Hope this is helpful to others.