Technical Constraints (OpenInsight 32-bit Specific)
At 15 AUG 2003 08:42:39AM Godfrey Farrugia wrote:
I'm using OI32 and I have come across a problem which I suspect has something to do with form constraints/limits. In a lostfocus of an object, I'm creating two different arrays successively on-the-fly, using the Utility('CREATE') statement.
If I create any one of them I have no problem, but if I try to create them successively, one immediately after the other, OI responds with a problem and I have to quit.
Q1. Are there any limits to how many arrays (edit-tables) I can create on-the-fly?
Q2. Is there a practical limit on the number of Columns/Cells I can have in any single array within OI32?
Q3. COLSTYLE returns a VM-delimited list of contents. Can anyone tell me what the first value of value 31 (i.e. column width) contains? Whereas I can account for all successive sub-values having a one-to-one correspondence with my array, the first sub-value is a mystery to me? Could it be the width of the row-numbers column, but I'm not showing it in my array?
Q4. What are the maximum number of objects I can have in a form?
Thanks and regards,
Godfrey Farrugia
At 15 AUG 2003 12:45PM Richard Hunt wrote:
I have used this value as the "width of the row-numbers column". I have no way of verifying this with documentation. Although I do use its value to expand, contract, and center the edit table within the form. And it does work fine so far for me (OI ver 4.1.3)
At 15 AUG 2003 01:13PM Revelation Technical Support wrote:
Godfrey-
You are doing this on a development version of OpenInsight, correct?
Performing such actions in a runtime system is a violation of license.
Thanks-
Revelation Technical Support
At 15 AUG 2003 07:04PM Richard Bright wrote:
Godfrey,
I'm puzzled why your design requires the creation of edittables on the fly - quite apart from being only acceptable on a development system. Typically one just makes visible pre-existing controls as needed. An easy way to do this is to have a multi-page form with main controls on first page - fixed like a tab control, and 'dynamically created' contols appropriately positioned on sucessive pages. The effect is the same as hiding/making visible controls.
Richard Bright
BrightIdeas New Zealand
At 15 AUG 2003 07:20PM Don Miller - C3 Inc. wrote:
That's what we do too. Depending on what happens on the first page, selective edittables are visible on subsequent pages. Doesn't violate the Run Time license either.
Don M.