Hi magicians Did someone notice buggy behavior in resident online tasks in XPA 3.2a? I experience crashes, especially when called for a 2nd time, while in the 1st call the user has modified the data-v

Hi Steven I guess you mean that you install on a test machine and then you just copy the folder to any machine you need Magic, right? I remember, in Unipaas it was necessary to install it (or some reg

Hi magicians A couple of months ago, being very optimistic, we upgraded our XPA desktop app on 40 windows tablets from 31b to 32a. Now we are forced to revert back: the last 2 months many bugs have be

More info on the issue and a workaround: In XPA3.2a form (desktop app), a table-control will stop responding to mouse wheel, the moment it "stumbles" on a row where all contained controls are non-park

Finally it seems to be an XPA 3.2x only issue :-( I reversed to XPA 3.1b and it works OK there

Hi Keith Already did. Mouse-wheel in general works Ok. It happens only in certain occasions Avgerinos

Hi magicians Struggling for the last 4 hours with a strange behavior of a table-control in XPA3, becoming insensitive to mouse wheel (tested so far on Win7 and Win2008Server). Same table, exactly same

David I cannot see why SQL-Express can not be used as an example: you can sure use it to compare the same application in different magic versions, hitting the same db under similar traffic conditions.

Thanks Arch That did it

Never experienced such a huge speed improvement in database speed - not even something close to this. So far, we did not notice any speed difference accessing MSSQL databases, at least in the 2 major

Hi magicians Anyone knows how to avoid the error regarding "ExcelPIA.dll" assembly when starting XPA3.2a? The dll is there but probably it fails to load (maybe because there is no office in this machi

Suggested solution does work always A better solution is to add a condition to temporarily "unlink" the string variables from the ItemsList and DisplayList properties while updating them.

Correction: message refers to tab-control and not to combo-box

Hi magicians Documenting an incompatibility in behavior of combo-box controls between XPA3.x v/s prior versions: Desktop app form contains a combo-control, with bot ItemsList & DisplayList properties

Hi Graham You 're right - my suggestion referred to desktop apps. Is that browser-control you mention as Magic control? Regards Avgerinos

Yes, it's obvious they have moved their focus to mobile. Desktop apps practically have nothing to gain - only to lose

Hi Graham The only solution I know is a nice trick that was mentioned here some years ago (yes this group is really magic! ) Tried it with uniPaaS & XPA3 and it works fine with both ActiveX and .NET b

Hi Pavel XPA3 is probably a wrap that encapsulates both old and new libraries. This is why it's almost double in size than it was Major functionalities are still served by the old engine, and this is

Thinking did not protect me from undocumented bugs. The only way I found was the hard way: Don't trust and test. And test and test and test and test... BTW, just stumbled on another issue. These combo

Also one vote for signing components. Insecurity was the reason external components were rejected by our global IT Avgerinos