Last page of a Browse doesn't display

[Keith]

HI

I have a Browse which for all money looks utterly standard.  There are 10 records per page and the standard 'First', 'Previous', 'Last' etc buttons.

The problem is that the last page wont display.  There are 40 records in the table and after 3 'Nexts' the browse greys out and freezes.  It can be reactivated with 'First' but the last page wont display.

Other similar browses do not have this problem.  It is not browser dependent.

Any tips?

Thanks

Keith

[Bruce]

my guess is that you have ticked on "allow xhtml" on one of the columns, but you are not checking that the data you are trying to display is actually valid. You can confirm this by opening the Firebug console in your browser, and then clicking on "Next". I expect you will see a javascript error reported on the last page.

Cheers
Bruce

[Keith]

H Bruce

Checked all of the fields in the Browse and no 'Allow HTML' is checked.  Opened Firebug as you suggested and got no errors - see attached picture.

Thanks

Keith

[attachment deleted by admin]

[Bruce]

then I'd need to see an example to duplicate the effect here.

cheers
Bruce

[Keith]

Bruce

Attached is a zip file with app dct and a file. 

You can login with anything in the three fields.

I have stripped this down to the 'Original' Browse (the one I said didn't display the last page) and a newly wizarded Browse on the same file to which I have done nothing except delete most of the file fields.

Both of them exhibit bad behaviour as regards display 'next' etc.

Thanks for looking at this and am very interested in the answer except if I have done something really stupid!

Cheers

Keith



[attachment deleted by admin]

[Bruce]

Hi Keith,

I don't think you've done much "wrong" - but thanks to the example I can see the cause of the problem.

You have the app set to "Store Data as" utf-8, but some of the data in the table itself is not valid utf-8. The class wasn't allowing for this, and so at that point it got a bit knotted.

So, for the 8.36 build I've added some code to deal gracefully with invalid utf-8. (it basically assumes ASCII in that case.)

On your side you may want to rethink whether the data should be "stored as" utf-8.

cheers
Bruce

[Keith]

Hi Bruce

The data for that table was loaded from an Excel spreadsheet so I can see how this has happened.

Thanks for the explanation.  Another trap to watch out for.

Cheers

Keith