or variable forms. Once it is read, it has no connection to the db. Even RBDOS is happy once it reads a form it does not need the definition anymore. It has been like this for as long as I can remember. It's nice to be able to push a new form definition in and have the nex person who uses it get the new version.
Dennis -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Javier Valencia Sent: Tuesday, September 21, 2010 4:46 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: So you can disconnect while in a bound form? In 7.5 you were/are able to load a new version of a form even if the form is in use. When the user closes the form and opens it again, the new version is displayed; great for updating forms and reports on a live database. Having said that, I was not aware that you could disconnect, set multi off, reload, set multi on, and reconnect from a form...I thought that is what External Forms were supposed to do... Javier, Javier Valencia, PE 913-829-0888 Office 913-915-3137 Cell 913-649-2904 Fax [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mike Byerley Sent: Tuesday, September 21, 2010 4:24 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: So you can disconnect while in a bound form? I don't know about earlier versions, but for certain in 7.6 ever since the form and code is loaded into memory in one go. With the form so loaded, the umbilicle cord can be cut without a problem. If you think about it, while you are disconnected, another user could delete your form from the db and your instance of the form would still work until you exited. ----- Original Message ----- From: <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, September 21, 2010 5:06 PM Subject: [RBASE-L] - So you can disconnect while in a bound form? >I was just now checking out something that another consultant did on a > windows 7.6 form, and I'm frankly shocked! I always assumed that if you > tried > to do something like disconnect / connect / reload while you are still > sitting in a form that is tied to a table, that you would get some kind of > error > like "invalid eep command" or something like that. > > But this guy has a group bar menu option for "reload the database" that > does a disconnect, connects in single-user mode, does an autocheck, does a > reload... all while still technically in that main menu form that is > bound to a > table! When done the program reconnects in multi-on mode, and does a > "return" back to the form and all is well. > > I really thought you could NOT do that, but apparently you can! He says > the client's been using that for database maintenance for years! For > bound > main menus, I always exited the main menu form, did the maintenance using > large, different-colored pause boxes for status updates, then reconnect > and > come back into the main menu. Does anyone see a downside to doing it > the way > he did? Does anyone else do this while still inside a form? > > BTW: yes I know that an external form file would take care of all these > issues... > > Karen >
