Razzak: It actually did occur to me that since it is an external file, that you could not modify it while it is "busy". It did, however, let me save my changes while I was in the form designer. It did not give me a "can't save, file is busy" message so I thought my changes were successfully saved. Then I saw the 0 bytes... ooops.
So then I guess to be on the safe side, you're suggesting that we should not be making changes to EFFs while people have them up? That's a design decision that each of us would have to carefully weigh. For databases where the main menu is static and hardly changes, that would be great. In this case the client just upgraded to 9.1, we're finding all kinds of little things we'd like to change throughout the day but we'll have to kick everyone out in order to safely make the changes. Thanks for the confirmation of what I suspected! Karen > Karen, Jan, et al., > > R:BASE External Form File (.rff) is an external file, as it is. > > So, how would you expect to open it, make changes, and then try > to save it while everyone else on the network is running the > application by accessing the same external form file? > > What happens when you RUN any "external" command file, or EEP, > when everyone else is running it, and then EDIT the file, make > some changes and then try to save it? > > That simple exercise should provide you with some very practical > and intelligent answers. > > Very Best R:egards, > > Razzak. > >
