Problem with A5v8 app running in A5v10

[Citadel]

More of a general question really ...

As I understand it, there is supposed to be a backward compatibility between versions so that older apps can be run, and redesigned, in the latest software release (A5v10).

However, since some parts of A5 have been redesigned, I imagine that we can expect some parts of an older app to just not work in v10.

My question to those that know v10 is, what areas of a v8 or v9 app are likely to be 'broken' by running it in a v10 environment.

Specifically, I have a tiny v8 app that consists of just 1 table, 2 embedded browses and a tabbed object (just 2 tabs). It loads under v10 okay, but as soon as I click on the second tab, A5 instantly closes and I'm back on the desktop!!

Now, maybe, this is an opportunity to learn about the new debugger, but I thought I'd ask a general question - what is likely to work in v10 and what is likely to not work.

Hope this makes sense.

[Tbaker]

Re: Problem with A5v8 app running in A5v10

Alan

I would not hazard a guess at this time what could be broken from V8/V9 into V10.

Most of the beta testing involved web applications and very little of the new desktop items. In a post here on the board, Selwyn advised that the V10 beta did not have the new browse code - so while you could test somewhat the "new browse" in V9 , it was not present in the V10 beta.

In your tiny app you have, the tabs and the browse have been issues in the past - not saying that it is an issue in V10 now - just what has happened in the past supported by many postings to this forum.

I have several apps that have both tabs and browses (and tabs with browse) and in testing with v10 so far, they have not had a problem, but my tabs and browses are pretty general (invoicing, inventory management, and job assignments just a few). I have had the full v10 release since October 1 - and I am currently working on two major apps - while I had seen some timing issues they were caused by changing some code in the original apps - and could be repeated in version 9 with that code - so I cannot blame V10 nor say it was a bug.

I think that what we all will have to do is to watch this forum to see what comes up and then deal with them appropriately in our own apps (or wait for bugs (which there will be some) to be fixed and then try again.

In my opinion it will be wait and see - will it follow the older versions in relationship to "BUGS" or will it be more stable - stability is what I am hoping for.

As far as your problem, if you want to have it tested here in the forum , work up a stripped down sample and post it. There will be a lot help offered as you know.

Sorry I could not give you more information, but if it was a web question, you would have been inundated with reponses, since most what was originally tested in V10 was web related.

Tom Baker

[Keith Hubert]

Re: Problem with A5v8 app running in A5v10

Hi Alan,

I have run Alphasports V9 with full version of V10 and tested the tabs on the Products form, it works perfectly and does not crash out.

I suspect there is an issue on your form which you have got away with but V10 doesn't like.

As Tom has suggested, post a sample here and maybe we can solve it for you.

[Citadel]

Re: Problem with A5v8 app running in A5v10

Thank you both for your replies.

On investigation, if it's not poor coding, I think perhaps that this is a v10 xbasic issue or maybe a timing issue. I had some code running whenever the form received focus and this was crashing the app. But it works fine in v8.

I've now stripped down the app and put the code on a button marked TEST. There are a lot of calculated fields and I have made a few adjustments to these. They no longer make logical sense but still work and may simplify any diagnosis.

When I press the TEST button the app sometimes crashes, but usually gives an error message (see capture.jpg) and when I press the TEST button a second time it always crashes.

If I change just 1 calculated field to a constant rather than an expression (see capture2.jpg) the app doesn't crash when the TEST button is pressed (The code just runs in the background so it looks like pressing the button has no effect).

There are a couple more issues in design mode ...

I cannot delete a column in the browse.
I cannot select either the text box labelled 'Control Panel' or the hotspot under it, UNLESS I use the object explorer.

Any thoughts?

[csda1]

Re: Problem with A5v8 app running in A5v10

Hi Alan,

First, let me address your general question. In most cases there are no hard (repeatable) compatibility problems with A5 going forward from version 6 and up. However, if they are, they typically of two types.

If it is a code execution message, it means that a piece of an Alpha 5 built-in function written in XBasic has most likely been worked on between versions, and has some bugs.

If it is a crash or code exception, it is most likely a "C" version (basically compiled code written in C) of a function causing the problem. Sometimes there are issues when Alpha tries to convert an XBasic function to "C" type for speed, and misses a nuance of how each works.

For the Xbasic types (and I realize you may not be able to tell the difference), the best thing you can do is make sure every variable in your code is dimensioned. See my tips here. Also, don't use functions in "odd" ways. Also use parenthesis in expressions generously. It won't hurt, and it guarantees Alpha will evaluate an expression in a correct groupings.

Also, each time yuo resave an action script in a new version, it rebuilds the code, possible changing timing and or code that it executes. This can causes problems, as essentially the code is brand new, and may have been generated a bit differently, meaning it's untested. This is why I always suggest changing code to XBasic (and ideally to functions!) for final code.

Timing issues typically have to do with forms and other layouts opening and closing, with out proper consideration that they are opening another thread which has it's own timing, and thus you may access some value, before it exists (on opening) or after it has removed (during closing).

As to your expression, you are using the Sign() function which is a "C" function that is not used a lot (and hence less tested). You could have easily ued something "simpler" like Value<0. Also add parenthesis as in (value<0).or.(value>1).or.(X=y)

I hope this helps you a bit!

[Citadel]

Re: Problem with A5v8 app running in A5v10

Thank you for your excellent advice Ira.

I realise your comments apply to all development and not just this app.

That said, I've removed all reference to the sign() function. In fact I've now stripped the code and calculated fields down to almost nothing, to try and isolate the problem: just 3 calculated fields and about 5 lines of code under the TEST button. New zip file attached.

Any thoughts anyone?

[Tom Cone Jr]

Re: Problem with A5v8 app running in A5v10

Alan, do you get the same results if you do not nest your calc field expressions inside each other? i.e. if you express each calc field without using any other calc fields inside each calc field expression

[Citadel]

Re: Problem with A5v8 app running in A5v10

I've gone one better and now have only one calc field, but the problem persists. New zip attached.

Hey, at least it's consistent ... and can therefore be reproduced. But I'm assuming that others get the same results . . . if so I guess I'll submit a report to Selwyn.

Incidentally, I sent a bug report on a separate issue to Alpha earlier today and got a 'thank you' back from Selwyn a few minutes later. What other company thanks you personally for telling them their product has a bug. Amazing!!

[Tom Cone Jr]

Re: Problem with A5v8 app running in A5v10

Alan, I'm seeing the same results here, even when I build a fresh form entirely within vers 10. Recommend you submit formal bug report with sample database and instructions attached.

[Citadel]

Re: Problem with A5v8 app running in A5v10

Bug report duly submitted.

Thank you all for your comments and support.

[Citadel]

Re: Problem with A5v8 app running in A5v10

Just an update...

I had a notification from Alpha a couple of hours ago. All three of the problems I mentioned in this thread have been confirmed and fixed in 10 hours - and actually much less when you realise I sent the bug report while most of America was sleeping.

The crash was caused by a 'stack overflow' because the software was 'not checking for recursion in one place' . . . I'm not going to pretend I have even a clue what that means!!

But, once again, I marvel at how quickly reproducible bugs get sorted.

Outstanding response by the Alpha team. Well done people.

[fddizon]

Re: Problem with A5v8 app running in A5v10

Allan,

made some modification with your code under test button

[COLOR="Blue"]'if calc->C_sum_of_hours = 0[/COLOR]
[COLOR="Red"]if topparent:C_sum_of_hours.value = 0 then[/COLOR]
	ui_msg_box("Success!!","Script had ended normally!!")
else 
	ui_msg_box("Success!!","Script had ended normally!!")
end if

hope this helps