Currently I am displaying related diary entries using seperate portals for Companies, People and Projects. If it can be done is it wise to use one portal for all three and change the tablename and dataprovider for specific fields at runtime? I have found a getTableName function but cannot find a …setTableName function!
4xjbh:
Currently I am displaying related diary entries using seperate portals for Companies, People and Projects. If it can be done is it wise to use one portal for all three and change the tablename and dataprovider for specific fields at runtime? I have found a getTableName function but cannot find a …setTableName function!
Wise?..Can it be done?
This is why I never use portals! Portals are soooo FileMaker.
Use a form in an a tab panel instead.
You can use the same form as many times as you like, as long as you don’t try to use it twice on the same screen.
Portals are indeed more limited than tabpanels.
However , for simple display/editing purposes they are fine.
(no need the build a form ;o)
If these related entries are only for displaying data (no editing),
you might consider using the dataset object in the databasemanager.
The object receives the result of a query defined by you,
and can be displayed:
in a label or global with html
in a Jtable bean. (basically a table grid)
This bean will soon be available in the latest servoy 3.0 beta.
With this bean you will be able to also edit the datagrid, but saving changes back to the db will have to be scripted, since you’ll be bypassing the entire servoy SQL engine here.
default behaviour of (GUI related)beans in webclient will be that an image is
generated and displayed after each call with the bean.
In the jTable case this means “only working for viewing purposes”
At a later stage we might do some kind of conversion from jTable to html table to make it editable again. But that’s not on the planning yet.
Do you use mean a list view form with header/body?
You design the form the way you would like to look, with or without headers, footers. Doesn’t need to be a list view. You can put forms within forms, so the possibilites are endless.
4xjbh:
and how do you
use the same form as many times as you like
when the form is linked to a table…a table name you cannot change at runtime. Have I misunderstood?
I assume you keep all your diary entries in one table! Otherwise things may get too complex…
Using invisible tab panels you can swap form depending on what kind of record you are viewing by connecting a method to the onRecordSelect event of your base form. But try something simple first!