Denny,

I finally have the component working.  I had to tweak several views in order to get everything to work.  But I really appreciate all of the assistance. 

Some questions...

Is it possible to preload a default list of fields into the selected field list... like a default report pattern?

Is it possible to store the SQL generated by the component, and then recall that stored information as a starting point for other queries and still use the component?

Is it possible to put Values in the Original field list, that are not selectable, that could be used as headers to seperate the data fields logically for the user?

Are there other properties, events and methods that can be accessed that are not listed in the help file, or are those all protected?

Thanks again for all the assitance!

 

Dear Rick,

 

I am so glad to hear that things are going better.  I have addressed each specific question below.

 

Is it possible to preload a default list of fields into the selected field list... like a default report pattern?

 

Based on your next post, I think you’ve already found this; however, the routine you are looking for is: ParseSelectStatement.  The ParseSelectStatement can process anything created by the FilteredSelectStatement property.

 

Is it possible to store the SQL generated by the component, and then recall that stored information as a starting point for other queries and still use the component?

 

100%  Every piece of the SQL piece can be saved and restored.  It is important to note that the SQL can not be restored until after the data has been bound to the component.  Below explains what properties relate to restore methods.

 

The ParseSQLStatement method can restore any sql statement returned by the FilteredSQLStatement property.

The ParseSelectStatement method can restore any select statement returned by the FilteredSelectStatement property.

The ParseWhereStatement method can restore any where statement returned by the FilteredWhereStatement property.

The ParseOrderByStatement method can restore any order by statement returned by the FilteredOrderByStatement property.

 

Is it possible to put Values in the Original field list, that are not selectable, that could be used as headers to seperate the data fields logically for the user?

 

Not currently; however, I will pass that along as a suggestion to the new team who will be working on the component.  I like the idea…  Kind of a category type feature…

 

Are there other properties, events and methods that can be accessed that are not listed in the help file, or are those all protected?

 

Not currently…  One of the things we are looking to do with the next release is expose all of the nested objects.  That will allow developers more control over the behavior of the object.  That will help features from multiple language support to better control over the appearance of the object.

 

As you use the component, if you have any other ideas and suggestions please be sure to share.  We are always looking for ways to improve the component and provide a better value for our customers.

---

Danny Cooper
Team Leader, Aspose Texas Team
Contact Us

Again,  thanks for the help and quick feedback... Exposing some of the nested objects would be nice... one of my users would like to be able to change the text on the buttons that move the fields from the list to the selected list... we will live through it... would it be possible to create a new control class, inherit your component, and then override some of the non exposed objects or properties.. or is that too much like changeing your source... is the source available for an additional cost?

thanks again, and the more we get familiar with component the more i like it...

-Rick Fuschillo

 

Dear Rick,

 

I am so very glad to hear that things are still going well.  Thank you for all of patience and diligence in resolving everything. 

 

I personally have not tried creating a new component using the Aspose.AdHoc as the base component.  However, doing so would not violate any part of the license agreement, as long as you did not attempt to market the newly created component as a stand alone product.  With the nested objects of the AdHoc component not currently being exposed, I am not for sure what options you would have available by doing so.

 

A source license of Aspose.AdHoc is available for a price of $979 USD.  A source purchase provides one year of source updates as well as the licensing coverage provided by an unlimited license ( http://www.aspose.com/FAQ/#ls1 ).  Since you recently purchased you would be available to upgrade your purchase.  By upgrading the order you would only be responsible for the difference between your original purchase cost and the new cost.  If you are interested in doing so, please e-mail our sales department at sales@aspose.com …  They would be glad to assist in helping to upgrade the order.

 

Please be sure to let me know if there is anything else I can do to help, I am always more than glad to.

---

Danny Cooper
Team Leader, Aspose Texas Team
Contact Us