Hello Eros and Roberto,

I followed your discussion and imho I would not implement Office dependent issues such as COM_ExcelSetCells(). COM, yes but if the user knows the object model of the programs such as Word or Excel the user must reference the right object, method or property. If you use COM_ExcelSetCells() strategie you must implement the whole object model.

I would create a more abstract way of calling the object made available via COM, just as you do now.

I do not know how thinBasic is build internally but if you can use a dotted like construction without making it an object oriented language would be a bennefit.

Just like

[code=vb]dim pWdAppl as P
dim pWdDocs as P
dim pWActDoc as P

pWdAppl = ole.create("word.application")
pWdDocs = pWdAppl.documents
pWdActDoc = pWdDocs.Add()
pWdActDoc.name = "mydoctwo"[/code]

In this example the names of the objects and properties are exact the same as used in the COM object that is called. It doesn't have to be part of thinbasic. You can map them 1:1 to the COM object. If you make a mistake the property or object is not found. Methods can be handled as functions() such as the Add() method. Properties just as they are and handle collections like array's.

[code=vb]pWdActDoc = pWDocs(2)[/code]

It is just an idea.