Below code freezes my xBase ( + eXpress) app.

@ DCSAY . GET ..
VALID { |o, lChanged| lUpdated:= o:changed, .T. };

xBase version si 19.331

Is that a know bug resolved in any later patch ?

Under WinXP it works without any problem, but under MS SBS2003 app freezes
completely and I have to kill the job to release the system.

o:changed class variable under SBS2003 within combo box causes that.

Best regards

Toma

Toma¾,

>Below code freezes my xBase ( + eXpress) app.

As this might be an eXpress++ issue, you might want to post this in the
third-party news group, or even better, on Roger's web board.

>@ DCSAY . GET ..
>VALID { |o, lChanged| lUpdated:= o:changed, .T. };

Is the VALID clause's code block assigned to the oXbp:Validate Callback 
Slot in eXpress++? If so, from where is it called or more precisely, when
is that code block evaluated? Why do you not use "lChanged" in that code
block,  but "o:Changed"? Where does "lChanged" come from? I assume 
"lUpdated" is a Private or Public variable that is set for later use?

>o:changed class variable under SBS2003 within combo box causes that.

"o:Changed" is not a Class Variable, but an Instance Variable! There is a
big difference!

Are you sure that the application hangs? Have you debugged it? Where does 
it actually hang -- in which line of code? Do you have any Error Logs of
any kind?

Too many questions, not enough information!

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas@Aerospace-History.net
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---

> Are you sure that the application hangs? Have you debugged it? Where does
> it actually hang -- in which line of code?

Just in line, where o:changed is performed. That was tested with 
Dc_Debugqout() function before and after that line inside the validation 
code block and program never came to the second one.

> Do you have any Error Logs of  any kind?
No, it freezes that hard, that it is not made.

> Too many questions, not enough information!

You were right. And because of that I wrote two test programs, one in pure 
xBase++and the other in eXpress++.
The result: No errors on both programs on both operatins systems.

Interesting.

Because I have to remaind, that original program, that is much bigger also 
works without problem on WinXP, but not SBS2003 or SRV2000.

Solution: I took that part of code away and rely on other parameters.

Thank you Andreas for your kindly help and best regards

Tomaz