Bruce - Does This Make Sense ?

[zdpl0a]

Bruce,

I solved my browse problem - I think

Some of my address and customer data contained the '&' sign.

I load a memory table from the physical data that has changed once every 30 minutes.  Works fine.

I added a routine to convert the '&' to '+' and the browse now flows fine.

They had to have '&' in the data before. 

Thanks,
Dave

[Bruce]

If you have "allow xHtml" ticked on for the column, then it makes sense. If not, then the & should have been converted (to &) automatically for you.

cheers
Bruce

[zdpl0a]

The box was not checked for the column.  Tried checking it too - no go - the paging in the browse locks up.

Went ahead and compiled my customer app, which uses the same file, but was last compiled with PR17 - now it locks up on the file as I try to browse through the file

Add edthe substitute routine to the customer site and it removed & and replaced them with + and it works.

Dave

[zdpl0a]

Let me correct myself - I cheated the problem.

I went to example 31 - Accounts and modified a customer record that does not appear on the first page of the browse with the ampersand sign.  The browse will not go forward and open up the next set of records, with with the &.

Also, you can not page back because of the very first record in the cvustomer file. 

Dave

[kevin plummer]

I'm having the same problem with the & in a a desc field on a browse with the next\last buttons not responding.

Removing the & makes the problem go away.

Allowing xHTML in the column made no difference.

[Bruce]

fixed in PR 26

[zdpl0a]

Thanks a bunch Bruce,

This one was really going to be a problem with a few customers....

Dave