Major browse issues after upgrading from version 8

[Nathan Zeiset]

I have recently upgraded to version 10.5 from version 8. We are experiencing frustrating problems with embedded browses when accessing the application over our local network. The application runs fine on the local computer.

I'll start with one issue. Again, this only occurs when accessing the application over our local network. Our invoices form (based on a set) has an embedded browse for the lineitems. If I click on a lineitem and delete it, A5 does not respond for several seconds. If I check the task manager, the memory used by A5 climbs quickly to about 1.8Gb, and then drops back to normal, at which point A5 begins to respond again. This occurs on a Win7 computer. (On another computer running XP, just before the memory usage reaches 1.8Gb, A5 crashes. I suspect this is due to memory limitations.) If I then try to delete another lineitem, this message pops up: "Memory corrupt - terminate operations."

If I open the default browse for this set, the problem disappears. I have already rebuilt the embedded browse on the form, which seemed to help some other issues, but it didn't help this one. So now I'm working on rebuilding the form, but that will take awhile. Do I have any other options? Is there another solution? If I have to rebuild all of the forms in my application, that would be overwhelming, indeed.

Nathan

[Ted Giles]

Re: Major browse issues after upgrading from version 8

Nathan,
I presume that you have reinstalled the V10.5 Runtime on the remotes if you are shadowing.
It is important that the RT and Dev build are the same release.
I believe that there were major changes to the Browses between V8 and 10.5.
Suggest you try "rebuilding" some of the Sets and Forms by going into Design Mode - change nothing - and resave.
You will need to keep a good record of what you have done.
I've often seen software situations where moving one version is fine - two and you have a problem. That's why I nearly always buy the current version.

[DORaymond]

Re: Major browse issues after upgrading from version 8

Yeah, I feel your pain. I feel like I am on the verge of loosing my job because of A5V10.

We have been using Alpha for more than 15 years to run our manufacturing business (about $20M per year size). 10 years ago I developed the application that we use now and was a "hero" because the software worked well and was custom to our specific needs. About 7 months back I began converting the application to V10.5 thinking that we don't want to be left behind with our app. based on old software. We have been using the new version for about a month and have had just one problem after another. I have had browse problems, report problems, index problems, network sluggishness problems, and on and on. Maybe if the app. was rebuilt from scratch I would not have as many issues, but it is way too big for us to do that now.

[Ted Giles]

Re: Major browse issues after upgrading from version 8

" Maybe if the app. was rebuilt from scratch I would not have as many issues, but it is way too big for us to do that now. "
Oh no it isn't!
The man who never made a mistake never made anything.
It might seem like a big issue, and it is for the business, but what do you think would happen if you told 'em to place it where the sun doesn't shine and use a proprietory application? They would be dead in the water.
Take a step back, deep breath and start solving problems.
1) what version did you go from to get to V10.5? It was a big jump from anything further back than V9.
2) get some help in to sort the problems out. There are loads of US guys itching to get involved, but it might cost a few bucks. (a few bob in the UK)
3) you were absolutely right to want to keep up with the latest technology, but if you see the tremendous contribution Stan Matthews makes to this Forum, you might want to slow down a bit.
4) if you need help in a particular area, just ask here on the Forum. Then you will be a hero once again.

[Nathan Zeiset]

Re: Major browse issues after upgrading from version 8

OK, time for an update. My first attempt at rebuilding the form resulted in the same problem. I deleted it and started over, this time simply copying the fields, etc. from the old form and pasting them into the new form. I couldn't copy and paste the embedded browse, so that was rebuilt from scratch, and now the problem described in the first post has disappeared. Strange that it worked for the second rebuild but not the first.

Unfortunately, there is another problem. This occurs on both the local computer and the networked ones. Here goes:

The invoice form is based on invoices.set, which has Invoice Header as the parent table, with a one-to-many link to Invoice Lineitems. The linking field name for both tables is Invoice_Number. Referential integrity is set to Cascade Changes/Deletes. There is then a one-to-one link from Invoice Lineitems to a table named "Cassettes", linked from a field named Index_Number in Invoice Lineitems to a field named Index in the Cassettes table. There is no referential integrity in this link.

In the embedded browse on the form for this set, the first two columns are Index_Number and Quantity from the Invoice Lineitems table, and the other two columns are Title and Speaker from the Cassettes table. If there are three lineitems in the embedded browse, when the last lineitem gets focus the first lineitem shows the title and speaker from the lineitem that has focus. It reverts back to displaying the correct title and speaker when the focus moves away from the last lineitem. If there are more than three lineitems in the invoice, the first one, two, three, or four lineitems in the browse may display the title and speaker of any of the last few lineitems in the browse when any of these last lineitems receives focus. Again, the display is corrected when the focus moves off of these lineitems.

I tried opening the set in design mode and resaving it, but the problem remains. This problem does NOT occur in the default browse for this set.

Both the development copy and the runtime are the current version.

Nathan

[Ted Giles]

Re: Major browse issues after upgrading from version 8

Nathan, the fact that the default Browse for the set works would suggest that there is something amiss in the Form somewhere.
From the details you provided, the attached seems to work OK.
Disect the construction of the Set.

[Nathan Zeiset]

Re: Major browse issues after upgrading from version 8

OK, I discovered the culprit. On the form properties, under the Filter/Order tab, I have the order expression for the Invoice_Lineitems table set to "Cassettes->Numindex". If I remove the order expression, OR if I use a field from the Invoice_Lineitems in the order expression instead, the lineitems display correctly in the browse, no matter which line has focus. The problem is... I really WANT the lineitems to be sorted on the "Cassettes->Numindex" field. What do I do now?

Nathan

[Stan Mathews]

Re: Major browse issues after upgrading from version 8

Try this on the onfetch event for the form

<browseobjectname>.QUICKSORTEXPLICIT("Your_column_title")

replacing <browseobjectname> and "Your_column_title"

with actual values.

[Ted Giles]

Re: Major browse issues after upgrading from version 8

Set the order in the Set options.

[Nathan Zeiset]

Re: Major browse issues after upgrading from version 8

I can't. In the one-to-many link in the set, I only have access to the fields in the child set, not the grandchild set. And since the link from the Invoice Lineitems table to the Cassette table is a one-to-one link, I do not have the option to set the order.

Nathan

[Nathan Zeiset]

Re: Major browse issues after upgrading from version 8

Thanks for the suggestion, Stan. I won't try it until next week, since it's quitting time here.

Nathan

[Ted Giles]

Re: Major browse issues after upgrading from version 8

Couldnt get it to work in the example I posted #6 Stan
BROWSE1.QUICKSORTEXPLICIT("INDEX_NO")

This works though when added to a button or the On Fetch command but keaves Focus on the Index_no in the Browse.
BROWSE1.activate()
BROWSE1.quick_sort()

Belay that first line. Works now I did it correctly. Doh!