Script fires twice

[[email protected]]

I have runtime solution running on a 2003 server with three XP boxes as clients. I have an "on change" event tied to the first field of a data entry form, social security number (SSN). After starting a new record and the SSN is entered an On change event (not ondepart)triggers if a matching SSN is found (in the same table) A dialog box appears asking if they want to still make a new duplicate record or go to the last record (branching action script). If they choose no, I delete the current record and take them to the last matching record where they should be able to edit it. Unfortunately the script fires again. I'm taking them back to the SSN field,yes, but no changes are made. If they choose yes to make a new record, the script duplicates the found record and gives it focus, unfortunately the script again fires.

My clients have tried taking the database off of the server and placing it on one of the three client boxes and sharing that with the same exact problem. So I feel we could eliminate server issues.


The sad part is that I am absolutely unable to duplicate this problem on my XP laptop using full version and I can't duplicate it on my 2003 server with an XP desktop using the runtime as the client, although my system is not multiuser. Everything works perfectly as designed. The odd thing is that this has worked properly on their system a few times, 98% of the time it fails, lately 100%.

My question is, has anyone ever had a script that runs OK on one system and not another? Is there somewhere I should start to look? I have checked the script over and over and sent them new updates without any changes in this odd behavior.

Thanks in advance
Bill Belanger

[martinwcole]

RE: Script fires twice

Bill, try this:
in autoexec, define a global variable
busy, logical

in your script, at the top, put
if busy
end
end if
busy=.t.
'your script
busy=.f.

some events fire more than once - and that may or may not be the problem

[[email protected]]

RE: Script fires twice

Thanks for the reply Martin.
I'm getting an error;

if busy
variable "busy" not found

It's probably a syntax error but I'm new to xbasic
Here's the whole scrip as adjusted

'Date Created: 05-Feb-2005 06:10:10 AM
'Last Updated: 05-Feb-2005 06:10:10 AM
'Created By : Owner
'Updated By : Owner

if busy
end
end if
busy=.t.

'Get 'Value' property of 'Ssn' in Form 'Application0' .
DIM GLOBAL vssn AS c
vssn = topparent:Ssn.value

'Conditional code follows. Executes only if the condition expression is True.
IF a5_eval_expression("=exist(Ssn,\"application\",\"Ssn_A\")") THEN
'Displays a message box (style:'Yes, No Buttons', image: 'Information symbol', id: 'On_file').
DIM SHARED On_file_result as N
DIM SHARED On_file_YES_Button as L
DIM SHARED On_file_NO_Button as L
On_file_YES_Button = .F.
On_file_NO_Button = .F.

title_var = "Social Security Number On File"
message_text_var = ""%text%
This social security number is already on file.

Click Yes to do a re-application

Click No to go to the last application to edit it.
%text%
On_file_result=ui_msg_box(title_var,message_text_var,UI_YES_NO+ UI_FIRST_BUTTON_DEFAULT+ UI_INFORMATION_SYMBOL)
'Test to see which button on the message box was pressed....
SELECT
CASE On_file_result = UI_YES_SELECTED
On_file_YES_Button= .t.
script_play_local("Re-App")
CASE On_file_result = UI_NO_SELECTED
On_file_NO_Button= .t.
script_play_local("GoToLastApp")
END SELECT
END IF

busy=.f.



This comment you made that events fire twice is a little unnerving in that it seems to be system dependent. Should this "busy" script be part of every developer's library? If true, shouldn't this be something Alpha would address?

Bill Belanger

[martinwcole]

RE: Script fires twice

Bill, had you previously declared busy as a global variable. If you dimmed it in autoexec, you will have to run autoexec for it to exist.

dim global busy as c

I know of no reason for the script to not see busy, but if you dim it in your autoexec script (which fires when the app is opened) - but if your are sure it exists, and you still get the error, at the top of your script say:
dim global busy as L
if busy=.t.
end
end if
busy=.t.

and busy=.f. as the last line in the script

this technique goes back about 5 years, so I don't know if its still relevant - but I would definitely try it!

Also, what happens when they answer one way or the other - do you take them back to that same field?

[martinwcole]

RE: Script fires twice

as I think about it, since they've already changed the value, at the top of where your script begins, set focus somewhere else, like
if busy ...


button1.activate()
your script

busyt=.f.

sometimes if its still setting there it may cause problems

[[email protected]]

RE: Script fires twice

I can do that. My real question is why are my clients having so much trouble with a databse that works perfectly for me? Is it possible fields are getting corrupted when I zip them the changes through email?

Bill Belanger