C'mon Dennis/Larry.. Who would put a database maintenance activity in the midst of a data entry scenario? That's a non-starter.

----- Original Message ----- From: "Dennis McGrath" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, September 22, 2010 9:26 AM
Subject: [RBASE-L] - Re: So you can disconnect while in a bound form?


Well put, Larry.
Dennis

________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig
Sent: Tuesday, September 21, 2010 6:52 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: So you can disconnect while in a bound form?


The problem isn't the connection to the form table, but rather to the table or tables bound to the form. Those tables may be in a state in which an unsaved disconnect would damage them.

In the kind of situation Karen described it sounds like the risk is minimal, but it still sounds like "getting away with something".
--
Larry


Sent from Yahoo! Mail on Android
Please excuse typing errors.


________________________________
From: Mike Byerley <[email protected]>;
To: RBASE-L Mailing List <[email protected]>;
Subject: [RBASE-L] - Re: So you can disconnect while in a bound form?
Sent: Tue, Sep 21, 2010 9:24:14 PM
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


--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, place any text to search for.
================================================


Reply via email to