[RBASE-L] - Re: VariableRadioGroup locks up

[MDRD]

Thanks Jan

Since V1 2 3 worked I figured it was my code logic.
I will look for that doc

Marc


  ----- Original Message ----- 
  From: jan johansen 
  To: RBASE-L Mailing List 
  Sent: Wednesday, February 25, 2009 7:50 AM
  Subject: [RBASE-L] - Re: VariableRadioGroup locks up


  Marc, 
   
  I would not look at your code but his machine. 
  If it works on your test then you need to find out 
  why it fails on his. 
   
  Is this a compiled app? 
  How many results are there in V4? 
  Did he install it or did you? 
  What is his operating system and memory? 
   
  Actually RBTI placed a troubleshooting document 
  a few months back. Find it and use it. 
   
  Jan 
    


    -----Original Message----- 
    From: "MDRD" <mdrd...@sbcglobal.net> 
    To: rbase-l@rbase.com (RBASE-L Mailing List) 
    Date: Wed, 25 Feb 2009 07:44:16 -0600 
    Subject: [RBASE-L] - VariableRadioGroup locks up 


    Hi 
     
    Of course the timing stinks on this.  I have a group of offices wanting to 
update 
    to V8, I sent them a form that works great in 7.5 to show them where we are 
going 
    with our app and the form works great on my 2 computers but this one office 
says his 
    computer locks up when he press V4.  He is the ring leader of this group 
and I am adding 
    some of his design requests.  When I get this fixed I will have a core 
group that is sticking 
    with me and Rbase compared the others that are wanting to switch to that 
other program. 
    (that other program Still is not our the door running after 2+ years) 
     
    I am using a VariableRadioGroup with V1 V2 V3 V4, when you press these it 
    looks up your custom names for the Buttons on the form.  So if you had a 
restraunt 
    you could press V1 for main dishes, V2 for sides, V3 for pies and cakes and 
V4 for 
    coke, Mr Pib.  and all the button names would change,  Click a button and 
if the 
    name of the button matches a charge code it is entered. 
     
    I can click V1-4 on my computers but his locks up on V4 
     
    This is a sample of my code, the only difference between v1-4 is changing 
the 
    number.  Should I use different Var for Vbutt Vnew Vhint and different 
cursors? 
     
    Thanks Marc 
     
     IF vbutton = '3' THEN 
       SET VAR vbutt TEXT = NULL 
       SET VAR vnew TEXT = NULL 
       SET VAR vhint TEXT = NULL 
       DECLARE cursor1 CURSOR FOR SELECT butname,v3,v3hint  + 
       FROM spbutton WHERE v3 EXISTS ORDER BY butname 
       OPEN cursor1 
       FETCH cursor1 + 
       INTO vbutt INDICATOR vi1, vnew INDICATOR vi2, vhint INDICATOR vi3 
       WHILE SQLCODE <>100 THEN 
        PROPERTY .vbutt caption .vnew 
        PROPERTY .vbutt color 'white' 
        PROPERTY .vbutt hint .vhint 
        FETCH cursor1 + 
        INTO vbutt INDICATOR vi1, vnew INDICATOR vi2, vhint + 
        INDICATOR vi3 
       ENDWHILE 
       DROP CURSOR cursor1 
     ENDIF 
     
     IF vbutton = '4' THEN 
       SET VAR vbutt TEXT = NULL 
       SET VAR vnew TEXT = NULL 
       SET VAR vhint TEXT = NULL 
       DECLARE cursor1 CURSOR FOR SELECT butname,v4,v4hint  + 
       FROM spbutton WHERE v4 EXISTS ORDER BY butname 
       OPEN cursor1 
       FETCH cursor1 + 
       INTO vbutt INDICATOR vi1, vnew INDICATOR vi2, vhint INDICATOR vi3 
       WHILE SQLCODE <>100 THEN 
        PROPERTY .vbutt caption .vnew 
        PROPERTY .vbutt color 'white' 
        PROPERTY .vbutt hint .vhint 
        FETCH cursor1 + 
        INTO vbutt INDICATOR vi1, vnew INDICATOR vi2, vhint + 
        INDICATOR vi3 
       ENDWHILE 
       DROP CURSOR cursor1 
     ENDIF