I have visited many of the posts about the issue of limited rows in edit tables but may be missing something. In our app we can only add 35 rows of information to an edit table. There is no row limit set for the edit table and there are only 5 columns whose data are limited to 7, 4, 25, 7 and 11 characters. How is this exceeding 64k? Or is it?
Thanks,
Blair
Blair
Check the following things. Set the Row Limit to -1 - click the More button for the DB Table to select this. For each item in the table, set the data length to the number of characters that you will store there. The default value for items is set to 80 characters by default. Data tables store data in FIXED length strings (including trailing spaces). This can eat into the 64K space quickly.
Don Miller
C3 Inc.
Thanks for reply Don. Before setting setting the Row Limit to -1 I wanted to know why I had a problem at 35 rows. The total amount of data is set to 55 characters for all the column. 55 x 32 rows < 64k, No?
Hi Blair
You don't get 64KB in a default edit table setup, you only get 32KB and that includes the formatting characters and presumably whatever OI uses to tell columms and rows apart. So it is quite easy to run out of room.
The -1 parameter is very handy for getting more room. I still think it has a 64KB limit, certainly if you have bound the table to a record you will have a 64K limit (for relatively unformatted data). The -1 parameter is linked to computer RAM, so you may find the number of rows you can now enter depends on how much RAM is available on the computer that you use.
I did a combination of the -1 parameter and unbinding the table and using my own code to load my edit table and save it, and found that I could increase from around 40 rows of 10 columns (mostly money ie $123,456.00) to 700 rows on the record (12345600) before exceeding the 64KB record limit. What I really needed was a separate table for my rows, and then I could have had as many rows as I liked (using my loading/editing/saving/paging code). It was about this point that we drew a line in the sand due to financial constraints. The perfect system costs an infinite amount of money.
Scott
Scott,
Thanks for the thoughtful and most informative response. Thanks for the explanation of how the ?1 parameter works. We will give that a try. Good day!