I totally agree The new compiler does have great advantages.
You can incorporate all your forms, labels, reports, RGW files, CMD files etc into it. The result is one EXE. Updates of the database - as long as there is no structure change - are almost obsolete Tony From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: maandag 7 maart 2011 19:45 To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Question about external form files Why not compile it into the EXE so every session one has its own copy and the problem goes away? Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] _____ From: [email protected] [mailto:[email protected]] On Behalf Of A.G. IJntema Sent: Monday, March 07, 2011 12:33 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Question about external form files I have had this experience with 9.0 in 2010. But this problem has been solved by RBG9 RDCC Staff a long time ago, However I must admit that I am still very keen on it by making regular copies of it. Tony From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: maandag 7 maart 2011 17:44 To: RBASE-L Mailing List Subject: [RBASE-L] - Question about external form files I'll tell you the truth -- I only have one client who is using an .rff form as their "main menu", and this is the client we just finished upgrading to 9.1. While some users were in the system, we made a change to the external form file, saved it with no error. Now the .rff file is showing up as 0 bytes and no one else can get in, we can't bring it up in design. Had to get everyone out and bring in a backup copy of the .rff file So... does this mean that you cannot make changes to an external form file while others have it open? I've seen this in the past going back to 7.6 when you try to copy over a file that's busy; it seems like it made the copy but then if you looked it would show 0 bytes and be corrupted. Karen
