>>>I have a class (sqlclsss.vcx) included in my executable that I instantiate the object like this:
>>>
>>>

>>>SET CLASSLIB TO sqlclss ADDITIVE
>>>lcSqlConfgConn = 'oConn'+TRIM(sqlconfg.product)  && example would be 'oConnFire'
>>>&lcSqlConfgConn = CREATEOBJECT("SQLCLSS.SQLPROC")  && sqlproc has methods and properties  <  -- ERROR HERE
>>>

>>>
>>>The class is included in the executable and it works on my development machine, but not on the client's. any ideas why? It returns a bad command verb error.
>>>
>>>NEWOBJECT() fails as well with the 'Unrecognized command verb' error.
>>
>>It seems the variable on the left doesn't exactly contain a valid variable name. Can't you wrap this in a try-endtry and log all the properties of the exception object? Also, log the contents of lcSqlConfgConn just to make sure that it contains what's inside.
>>
>>The other possibility is that the COM object has some error inside itself, or that the error is actually bogus. Someone correct me if I'm wrong, but the "library.class" syntax in createobject() is reserved for COM objects - if you're instantiating from your included class, you should have just the class name.
>
>I just put a new exe out there for them to test with it all wrapped inside a try..catch...endtry with the error object properties being written to a logfile for me including the value and type of variable for lcSqlConfgConn.
>
>The other possibility has me thinking....

To test that other possibility you only need to try to run your exe on any machine where sqlclss is not registered. Or you can temporarily try to unregister it on your machine. One of those would simulate what I suspect may be the case.