Karen: You'd mentioned in your first message: "Client says this happens
in a couple forms, but was sporadic", and nothing to suggest there's a
"beat" to these episodes. Reminds of the good old days before PC power
conditioning (UPS) became affordable. Voltage didn't/doesn't have to
wander far off the mark for the ghosts to take over. SafeSectors was
started, in part, to mitigate this very risk.
So how's the grid in your client's area? Large wind farms? Any large,
intermittent machine loads (e.g. HVAC) on the same breaker panels?
Double-bussing on those panels? Has their infrastructure team paid
attention to electrical integrity? Are server(s) and all network fixin's
fed by reputable (e.g. APC), well-maintained UPS units? How 'bout
workstations? Or are they relying on off-shore, off-brand surge strips?
This is all certainly topical in California, where electrical chaos is
the order of the day.
Best, Bruce
Bruce A. Chitiea
SafeSectors, Inc.
1142 S Diamond Bar Blvd # 442
Diamond Bar CA 91765-2203
[email protected]
(909) 238-9012 m
------ Original Message ------
From "'Karen Tellef' via RBASE-L" <[email protected]>
To "[email protected]" <[email protected]>
Date 4/23/2024 6:24:25 AM
Subject Re: [RBASE-L] - Disappearing text - an interesting discovery
Not a solution to my problem, but we did "discover" the command SET
REFRESH [x]
The help description:
SET REFRESH specifies how often R:BASE refreshes the form or the Data
Browser, and displays current data. It also automatically recalculates
lower tables in forms. Specify zero to turn the setting off. When
REFRESH is set off, R:BASE tells you of edits when you save or delete a
row.
So this is like the "auto save" that we've been talking about.
The default is 0, and I checked all the programs and forms and we don't
set or change it. I checked the value going in to the form and it is
at 0. I put a 'set refresh 0' before bringing up the form, just in
case, and it still disappears
Karen
On Monday, April 22, 2024 at 11:20:15 AM CDT, jan johansen
<[email protected]> wrote:
Karen,
I do not know the answer to the network but I have seen enough
strangeness over networks to question it.
Currently on my network there is a large slowdown that occurs at random
that I haven't been able to pinpoint.
Maybe Mike Byerly can shed some light on network vagaries, like random
polling and such.
Jan
From: "'Karen Tellef' via RBASE-L" <[email protected]>
To: "[email protected]" <[email protected]>
Date: Mon, 22 Apr 2024 14:54:38 +0000 (UTC)
Subject: Re: [RBASE-L] - Disappearing text
Jan: I don't have it here at my place. It has sensitive data so I
work while connected remotely. So it happens to them on the network,
and to me while dialed in (VPN). I could copy it down locally but
it's a massive database
But you gave me an idea to try. I brought the table definition and
the form here to my environment. Made sure I ran the exact build of
RBase as they are. Did the "edit using", sat on a field and waited,
and the text never disappeared. So doesn't appear to be a form
setting
Can a network fire off a "save work" command?
Karen
On Monday, April 22, 2024 at 09:37:26 AM CDT, jan johansen
<[email protected]> wrote:
Karen,
Along the line of Jim's question, does the form exhibit this behavior
running on your development environment i.e. not running across a
network?
Jan
From: "'jim schmitt' via RBASE-L" <[email protected]>
To: 'Karen Tellef' via RBASE-L <[email protected]>
Date: Mon, 22 Apr 2024 14:21:29 +0000 (UTC)
Subject: Re: [RBASE-L] - Disappearing text
Karen:
do you get the error if you do the 'edit using' from an R: prompt ?
or is the form in question being called by another form ?
JIm
On Monday, April 22, 2024 at 09:03:46 AM EDT, 'Karen Tellef' via
RBASE-L <[email protected]> wrote:
Javier:
I think you're getting close. Yep, I'm aware of the need of a dummy
space to land so that it saves your final entry. So that RBase
doesn't think that you've exited the field without wanting to save
the value. But a "landing spot" isn't going to help here because if
the user is taking a long time to type in the big memo field, it will
blank out the field as the person is typing. It isn't based on
inactivity. That's why they type outside RBase and copy it into the
field.
So yeah, it's as if there's an "auto save" somewhere and it thinks I
don't want my final value because I haven't moved off the field. But
is there such a thing? If so, that's news to me.
And remember, it only happens in variable edits, doesn't happen in DB
edits.
There's no form timer. I don't think there's a form timer anywhere
within this application. The 30 seconds is a guess, it can happen
earlier than that or later than that (I have waited up to a minute
before it happened). There is a SET TIMER in the app, I think set
for a couple hours, but RBase isn't exiting in this case.
Yes, I need the values in those two variables after I exit the form
to be used in an email that will be sent after the form closes. The
variable data isn't saved anywhere.
So -- is there an "auto save" somewhere? Either a form setting or a
"SET" command that I don't know about? Otherwise since this doesn't
happen with DB edits, I will probably create a temp table and add it
to the form and turn these into DB Edits for the temp table.
Karen
On Sunday, April 21, 2024 at 08:03:03 PM CDT, Javier Valencia
<[email protected]> wrote:
EDIT USING is the only way I use forms and I don't have issues. What
do the variables do? Do you need them after exiting the form?
The fact it happens after 30 seconds would appear to indicate there
might be a timer that refreshes the form every 30 seconds, and if the
variable has not been saved it might reset it to the original,
unchanged value.
In the old days we used to place a dummy field behind the last
variable to provide a landing spot as was mentioned.
If the form is doing an auto save, there is a system variable you can
check to see if there are pending changes and stop the save and
return to the variable field with a message.
Javier Valencia, PE
Sent from my T-Mobile 4G LTE Device
-------- Original message --------
From: 'jim schmitt' via RBASE-L <[email protected]>
Date: 4/21/24 6:16 PM (GMT-06:00)
To: 'KAREN TELLEF' via RBASE-L <[email protected]>
Subject: Re: [RBASE-L] - Disappearing text
Karen:
Another thought......If you are using just variables on a form, the
last variable field will need to have another 'dummy field as the
form need a 'landing'.for the cursor (even if not used). I do
this all the time with variable forms, set up a dummy variable field,
that the screen never gets to after the last variable field.. Base
your exit or return after the field is entered.
Jim
On Sunday, April 21, 2024 at 06:11:42 PM EDT, 'KAREN TELLEF' via
RBASE-L <[email protected]> wrote:
Not sure what you mean. The variables are null going into the form.
User is required to type something in both variables
Karen
Sent from my iPhone
On Apr 21, 2024, at 4:12 PM, Bruce Chitiea <[email protected]>
wrote:
What happens if you define the variables as Form Variables?
Bruce
------ Original Message ------
From "'Karen Tellef' via RBASE-L" <[email protected]>
To "RBase List" <[email protected]>
Date 4/21/2024 1:15:36 PM
Subject [RBASE-L] - Disappearing text
Version 10.5. Client says this happens in a couple forms, but was
sporadic. Finally there's a form where the issue is easy to
replicate so I have something to work on.
Issue: if you type something in a variable edit field and are just
sitting in that field, if you wait about 30 seconds the text will
disappear. The value of the variable is truly null when you exit
the form.
Specifics:
1. Form is based on a table brought up with "edit using" on just
one row of data. No processing is done before the form is brought
up. Literally one line of code in the main menu option.
2. In addition to table fields I have a variable edit and a
variable memo. Both variables are initialized to null on the
form's before-start EEP, one is text type and one is note type.
3. The disappearing happens on both of the variable fields.
Whether you are on the text edit or the memo edit, they will
disappear. Only the one you are on will disappear; if you had
entered data in the other variable it sticks around.
4. Entering text into a DB Edit field and sitting on that field
will not disappear.
5. Doesn't seem to be a case of memory build-up. If you go into
the application and this is the first thing you do, it will happen.
Not just at end of day, after another heavy process, etc.
Weird, huh? But I can replicate it every time on this one
particular form
Because they often type long notes into that memo field, and they
aren't fast typists, they have been typing the notes in Word and
then copy/paste into the field and move off the field asap.
Karen
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/emeb2b1479-d72c-4412-a3ec-e9313bae07af%40a5dc929d.com.
