Raul wrote:

/*
Combo with item lookup would make sense to be a new separate control
(TButtonLookupCombo?) since it would not be compatible with this one -
and would need to store foreign keys instead.
*/

Understood.

--
Frederick

Frederick:

Yes this forum does provide feedback to Tim (hence my THtmlEditor shameless plug<again>).

I am not sure how the next version is going to deal with "reporting requirements" without Delphi web modules exactly.  I guess the ability to to send code to execute on the server will help - but format and layout will be a lot of work if you are doing all of this by hand.

The reality is that good programming tools are expensive.

I should do another case study, this time on how I build and deploy reports in EWB.  Since I use RTC it is a bit different, but it the same concept could be put into one EWB Server WebModule DLL which would be reusable in all projects.  

There are two parts:
1.   A program to build reports and store them into a database table.  (Table contains, report, query, and join relationships)

2.   A function in the server to get the record from the report table,  execute SQL,load reportbuilder report, print to device to get PDF and return it to client.  (This would be the WebModule DLL).

In EWB it becomes two lines of code per report. (to execute, and a few lines to assemble parameters).

 frmView.pluginView.URL := gbURL +  '/report?RPTNAME=' + sReport + sType + sDateRange + sPeriod;
 frmView.ShowModal;

The VIEW form has a TPlugin to display the PDF.

Walter

Walter,

/*
I should do another case study, this time on how I build and deploy reports in EWB.  Since I use RTC it is a bit different, but it the same concept could be put into one EWB Server WebModule DLL which would be reusable in all projects.  

There are two parts:
1.   A program to build reports and store them into a database table.  (Table contains, report, query, and join relationships)

2.   A function in the server to get the record from the report table,  execute SQL,load reportbuilder report, print to device to get PDF and return it to client.  (This would be the WebModule DLL).

In EWB it becomes two lines of code per report. (to execute, and a few lines to assemble parameters).

 frmView.pluginView.URL := gbURL +  '/report?RPTNAME=' + sReport + sType + sDateRange + sPeriod;
 frmView.ShowModal;

The VIEW form has a TPlugin to display the PDF.
*/

Thanks for the pointers.

In part 1, I suppose I could use Delphi 7. In part 2, Delphi XE+ will be needed. Are DBISAM components required to be installed into Delphi  XE+ for the DLL to be created?

--
Frederick