Xailer & OZ Software

Hi,
Example:
We have oDataSet_Articles in the main article window frm_Articles. When the
user want to browse the articles, he pushes the Browse-button and the browse
window (frm_Articles_browse) pop up (not modal).
It would be nice to also be able to call frm_Articles_browse as a
stand-alone window, i.e. with its own defined oDataSet_Articles and
oDataSource. It is just when the window is called by another one (not Main)
and are receiving a oDataSet (as a parameter?) the "built in"
oDataSet_Articles are substituted with the existing one.
The main reason for the browse pop-up window is to let the user choose an
article from the browse. I.e. K_ENTER==he chooses a new article, the
browse-window closes and frm_Articles are updated with the info from the
chosen article (new sort order/filters etc. set in the browse window are
transferred back to frm_Articles). K_ESCAPE == the browse-window closes and
nothing happens in frm_Articles (new sort-order/filters/current record is
reset back to what it was before the browse-window popped up).
I have played around with different approaches but can't get it work
properly. Could someone please give me some advise or push me in some
direction?
Thanks,
Paal

Paal,
We expect to have a new type of form call DataModules in the near future.
All the components inside those Data modules will be visible to any form.
Until then you should use the technique shown in sample DbfData2. Sorry for
any inconvenience.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:471387aa$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Hi,
>
> Example:
> We have oDataSet_Articles in the main article window frm_Articles. When
> the user want to browse the articles, he pushes the Browse-button and the
> browse window (frm_Articles_browse) pop up (not modal).
>
> It would be nice to also be able to call frm_Articles_browse as a
> stand-alone window, i.e. with its own defined oDataSet_Articles and
> oDataSource. It is just when the window is called by another one (not
> Main) and are receiving a oDataSet (as a parameter?) the "built in"
> oDataSet_Articles are substituted with the existing one.
>
> The main reason for the browse pop-up window is to let the user choose an
> article from the browse. I.e. K_ENTER==he chooses a new article, the
> browse-window closes and frm_Articles are updated with the info from the
> chosen article (new sort order/filters etc. set in the browse window are
> transferred back to frm_Articles). K_ESCAPE == the browse-window closes
> and nothing happens in frm_Articles (new sort-order/filters/current record
> is reset back to what it was before the browse-window popped up).
>
> I have played around with different approaches but can't get it work
> properly. Could someone please give me some advise or push me in some
> direction?
>
> Thanks,
> Paal
>

Paal,
We expect to have a new type of form call DataModules in the near future.
All the components inside those Data modules will be visible to any form.
Until then you should use the technique shown in sample DbfData2. Sorry for
any inconvenience.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:471387aa$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Hi,
>
> Example:
> We have oDataSet_Articles in the main article window frm_Articles. When
> the user want to browse the articles, he pushes the Browse-button and the
> browse window (frm_Articles_browse) pop up (not modal).
>
> It would be nice to also be able to call frm_Articles_browse as a
> stand-alone window, i.e. with its own defined oDataSet_Articles and
> oDataSource. It is just when the window is called by another one (not
> Main) and are receiving a oDataSet (as a parameter?) the "built in"
> oDataSet_Articles are substituted with the existing one.
>
> The main reason for the browse pop-up window is to let the user choose an
> article from the browse. I.e. K_ENTER==he chooses a new article, the
> browse-window closes and frm_Articles are updated with the info from the
> chosen article (new sort order/filters etc. set in the browse window are
> transferred back to frm_Articles). K_ESCAPE == the browse-window closes
> and nothing happens in frm_Articles (new sort-order/filters/current record
> is reset back to what it was before the browse-window popped up).
>
> I have played around with different approaches but can't get it work
> properly. Could someone please give me some advise or push me in some
> direction?
>
> Thanks,
> Paal
>