Attribute Style does not work with unlimited recs. in query

BLOMASKY

I have a query with paging and the columns with attribute styles work fine. However, if I allow unlimited records (and set an explicit height), then the attribute styles don't work. Is this just me or is this a bug? (errr, I meant undocumented feature...)

Bruce

BenHayat

BLOMASKY wrote
I have a query with paging and the columns with attribute styles work fine. However, if I allow unlimited records (and set an explicit height), then the attribute styles don't work. Is this just me or is this a bug? (errr, I meant undocumented feature...)

Bruce

Stay away from "Unlimited". Support had told me sometime ago, Unlimited will be deprecated. Could be gone in V7. I had several problems.

BLOMASKY

So, you are telling me that I have to have a good idea what is the MAX # of records that might be retrieved and limit my queries to that? This would be a "tad" limiting.

Assume my Inventory BO has 100,000 rows (pretty small), if the user opens a query that has filters and no filter has been entered yet. I would expect the users to be able to sort, Jump to the end, etc. (I know that the query is buffered and that all 100K records are not read and transfered to the client @ once. )

I did some testing, if I do put a limit in, (tried with 100), I can then scroll down to the bottom, but it looks like there are ONLY 100 records in the file then. There is no indication that there are more records nor is there a way to access them.

Does this make sense?
Is there a better way?

Thanks
Bruce

BenHayat

BLOMASKY wrote
So, you are telling me that I have to have a good idea what is the MAX # of records that might be retrieved and limit my queries to that? This would be a "tad" limiting.

Assume my Inventory BO has 100,000 rows (pretty small), if the user opens a query that has filters and no filter has been entered yet. I would expect the users to be able to sort, Jump to the end, etc. (I know that the query is buffered and that all 100K records are not read and transfered to the client @ once. )

I did some testing, if I do put a limit in, (tried with 100), I can then scroll down to the bottom, but it looks like there are ONLY 100 records in the file then. There is no indication that there are more records nor is there a way to access them.

Does this make sense?
Is there a better way?

Thanks
Bruce

I agree Bruce, I hope we get a better solution to this in V7. I was just sharing with you that the unlimited has some strange side effects. It also acts strange in Mobile too. But we need an alternative to "Unlimited".