I was saying do not include the path in the AddObject() with respect to runtime purposes only. During development, the path to your classes should be in your VFP search path. Since you do not hard code a path to your class in the AddObject(), the class does need to be in the VFP Search path during development only.

My assumption here is you do not test out everything from a compiled APP/EXE.

Anyway, did the code, This.MyColumn.Addobject('txtIncr','aabase01'),
work for you?

>Mark,
>Even though the Class is part of the project (I checked this) why do I still need to put it in a Path just for this command ?