Re: Screen not exiting properly

Tech-Archive recommends: Speed Up your PC by fixing your registry

Here is a copy of the email that I just sent to Andrew. If I'm not mistaken,
this is where the disabling/enabling of buttons is going on, and I should be
adding in code to keep the exit button enabled, and able to exit, correct?

Yeah, those functions are all in the sssch.prg.... and now that I'm typing
to you, I think I've found what's going on. Looking me right in the face...

FUNCTION readshow
PRIVATE t_ecole
IF m.adding
SHOW GET m.choix, 1 DISABLE
SHOW GET m.choix, 2 DISABLE
SHOW GET m.choix, 3 DISABLE
SHOW GET m.choix, 4 ENABLE

IF varread() = 'ECOLE'
SHOW GET m.save ENABLE
ELSE
SHOW GET m.save DISABLE
ENDIF

t_ecole = m.ecole
SCATTER MEMVAR BLANK
m.ecole = t_ecole
ELSE
IF eof()
GO BOTTOM
SHOW GET m.choix, 2 DISABLE
IF eof()
SHOW GET m.choix, 1 DISABLE
ELSE
SHOW GET m.choix, 1 ENABLE
ENDIF
ELSE
IF bof()
GO TOP
SHOW GET m.choix, 1 DISABLE
IF bof()
SHOW GET m.choix, 2 DISABLE
ELSE
SHOW GET m.choix, 2 ENABLE
ENDIF
ELSE
SHOW GET m.choix ENABLE
SHOW GET m.save ENABLE
ENDIF
ENDIF
SCATTER MEMVAR
ENDIF

If I'm not mistaken, those should just all be enabled ... or at least have
extra code in there that enables the exit button, right? I really need to
start glossing over the code before I ask questions, and look for things
that I should know lol. Still learnin'!

Matt
"Matthew" <mcuriale@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:egUBtZtbGHA.4892@xxxxxxxxxxxxxxxxxxxxxxx
I'll forward the originals to you and Andrew, I apologize for that. I
tried opening them up in vfp6 to see if it was the right ones.


"Cindy Winegarden" <cindy_winegarden@xxxxxxx> wrote in message
news:O8yAHEtbGHA.3824@xxxxxxxxxxxxxxxxxxxxxxx
Hi Matthew,

I looked at what you sent. In your original post you mentioned FoxPro
2.6a. What you sent was a Visual FoxPro form that looked like it was
converted from a Fox2x form. I opened it in the (VFP9) Class Browser to
easily see all of the code and this is part of what I saw:

PROCEDURE txtecole10.Valid
RETURN v_ecole()
ENDPROC

PROCEDURE cmgsave17.Valid
RETURN v_save()
ENDPROC

PROCEDURE cmgchoix19.Valid
RETURN v_choix()
ENDPROC

PROCEDURE cbotri20.Valid
RETURN v_tri()
ENDPROC

The conversion wizard would have put those functions in a PRG file
somewhere. Have you looked to see what's going on there?

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@xxxxxxx www.cindywinegarden.com


"Matthew" <mcuriale@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uQv9vYhbGHA.3908@xxxxxxxxxxxxxxxxxxxxxxx
I have tried to open all snippets, but that doesn't do anything...
Nothing opens, it just sits at the screen editor.

I can post the buttons/fields and their snippets here, if that might
help. Also, this only occurs when nothing loads into the screen. When
data is entered, or the fields are initially populated, all the buttons
work fine.

I've never heard of "obligatory" fields unless they were programmed
that way either in a Valid clause or by a Save button. Also, I've never
heard of buttons being enabled/disabled other than they were set to be
initially disabled and programmatically enabled later or the reverse.
I'd say there's a lot more going on in your Screen than you realize.
Have you tried choosing Screen > Open All Snippets from the menu?

In foxprow 2.6a, we have a screen ...if there is nothing in the
fields, all of the buttons are disabled. Exit doesn't work, and the
only way to get out of the screen is to either enter a school number,
or hit the escape key.

I've tried taking out the valid clause in the school number field, as
it is the only one with a clause,






.

Quantcast