Take my yes vote for changing forms and/or reports in a live database as well. R:Base will simply use the older form as long as it is in use, but the next time it is called, it will use the new one. The entire form is loaded when called, so there is no confusion. It an additional button is added, it won't magically appear on an open form, but will be there the next time the user calls the form.

Albert


On 3/18/2015 8:49 AM, jan johansen wrote:
I'm with Karen. Since 7.6 I have not any issues changing reports and forms while people are in the database.

    -----Original Message-----
    From: Karen Tellef <[email protected]>
    To: [email protected] (RBASE-L Mailing List)
    Date: Wed, 18 Mar 2015 10:29:45 -0400
    Subject: [RBASE-L] - Re: Compiler question

    I wouldn't agree with that.  I've never experienced a problem
    changing a form or report while
    someone might have had it open

    Karen
    -----Original Message-----
    From: Tony IJntema <[email protected]>
    To: RBASE-L Mailing List <[email protected]>
    Sent: Wed, Mar 18, 2015 8:58 am
    Subject: [RBASE-L] - RE: Compiler question
    Dan,
    To be honest I think there is also a risk changing reports / forms
    while users are busy.
    Tony
    *From:*[email protected] <mailto:[email protected]>
    [mailto:[email protected] <mailto:[email protected]?>] *On Behalf
    Of *Dan Goldberg
    *Sent:* woensdag 18 maart 2015 14:20
    *To:* RBASE-L Mailing List
    *Subject:* [RBASE-L] - RE: Compiler question
    I am sure you know the pros like securing your forms,reports,etc
    inside the exe.
    A con for me is if there is an urgent fix on an embedded report or
    form I cannot apply it until everybody is out of the compiled app.
    Which is not possible during work hours.
    If the report or form is with the database I can make the change
    and tell the user to run it again.
    I guess I can create a login script to copy the compiled app to
    the users desktop and go that route.
    Dan Goldberg
    *From:*[email protected] <mailto:[email protected]>
    [mailto:[email protected] <mailto:[email protected]>] *On Behalf
    Of *TOM HART
    *Sent:* Tuesday, March 17, 2015 7:53 PM
    *To:* RBASE-L Mailing List
    *Subject:* [RBASE-L] - RE: Compiler question
    Can you elaborate on the pros and cons?
    Tom Hart
    On Tuesday, March 17, 2015 6:05 PM, Dan Goldberg
    <[email protected] <mailto:[email protected]> > wrote:
    There is pros and cons to including them in the compiled app.
    Dan Goldberg
    *From:*[email protected] <mailto:[email protected]>
    [mailto:[email protected]] *On Behalf Of *TOM HART
    *Sent:* Tuesday, March 17, 2015 4:02 PM
    *To:* RBASE-L Mailing List
    *Subject:* [RBASE-L] - RE: Compiler question
    I do include them in all my compiled apps and would recommend
    others to do the same, makes updating much simpler
    Tom Hart
    On Tuesday, March 17, 2015 5:33 PM, Dan Goldberg
    <[email protected] <about:blank>> wrote:
    I would think they would not because they are separate
    applications. You would need to include them in both or just have
    them in the database.
    Dan Goldberg
    *From:*[email protected] <about:blank> [mailto:[email protected]
    <about:blank>] *On Behalf Of *TOM HART
    *Sent:* Tuesday, March 17, 2015 3:14 PM
    *To:* RBASE-L Mailing List
    *Subject:* [RBASE-L] - Compiler question
    If I have a compiled app that runs from a button on my main
    menu(which is also compiled), will forms, reports, etc carry to
    the app from the button.  I know that they all apply to the main
    compiled app, but do they to others
    Tom Hart


--
A democracy ..." can only exist until the majority discovers it can vote itself 
largess out of the public treasury."
Attributed to Alexander Fraser Tytler 1747-1813

Reply via email to