The CBO class is designed to work with your custom classes and not elemental .Net classes. Since CBO calles upon SystemActivator.CreateInstance to instantiate the custom object and since CreateInstance requires the object to expose a default (parameterless) constructor, you will not be able to use CBO.FillCollection to return List<string>. As for System.String not having a default constructor, I guess that makes sense because a string is immutable. Creating a new String() instance that cannot then be filled is of no benefit.

Although you could define a wrapper class around System.String, it would be much easier to manually loop through the DataReader returned by your DataProvider's GetWords method and add the single string from each row returned to the List<string>.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner