ISL Error :0

[Keith]

Hi

I have got this ISL Error: 0 after making the simplest of changes to my code.

I had a compiled program (no errors).  I added one field to a Tab on a form and get this error.  Take the field out and the error goes away.

Googling the error indicates that people think it has something to do with an improperly coded Return statement but that isn't certain.  Of course, I haven't added any 'Return'.

I had a problem with this Form a while ago because it has about  200 'fields' including Display and Buttons and it generated the 'Too many SEGDEFs' error but that was fixed after setting procedures per module to 1

This sort of error gives you goose bumps because you don't know what to do and wonder if it can be fixed at all.

Thanks for soothing words 

Keith

[Bruce]

it likely means you have too many fields on the form unfortunately. Time to reconsider the form to see if it can be simplified, or if you need to make use of the "form on form" functionality to break it down a bit.

cheers
Bruce

[Keith]

Thanks Bruce.  I will look into 'Form on a Form' and see what I can do.

In the meantime I can confirm that the error occurs because there are too many 'things' on the Form.  Experimentation showed that even removing a Display field was enough to remove the error.  I now have rejigged some of these Displays e.g. -

Old: Tyre Width: <width field> (mm) (1 prompt, 1 field, 1 Display)
New: Tyre Width (mm) <width field> (1 prompt, 1 field)

removes 1 'thing'  (not as elegant but functional).

Keith

[Keith]

PS

For anyone who has experienced the 'too many SEGDEFs' problem or the 'ISL Error: 0' problem I thought I would report that the whole solution is pretty straightforward.

Firstly, the 'SEGDEF' error may be able to be fixed by setting the number of procedures per module to something less than the standard (1 is excellent!).  This is because this error seems to relate to the number of 'things' in the module and even if a Form, say, has not many fields when you have 10 Forms in a module you can easily have more than the magic number (about 200).

If the problem persists and you are pushing 200 in a single Form then the solution is as Bruce has noted before - to place a Form on a Form.  Bruce has said previously (http://www.nettalkcentral.com/index.php?option=com_smf&Itemid=36&topic=5746.0) :

BTW - NT allows for a "form inside form" approach, and this will probably solve the Segdef issue.
the "sub form" can be on the file fields, but it should be a "memory form" (with the option to not generate the <form> tag).
Tab style for this form set to plain, save buttons etc turned off..

The thread is worth reading in full.

My own recent experience says that the ISL error is not just related to 'fields' but to 'things' i.e. all the buttons and Displays as well.  Remove 1 Display and you can add 1 Field.

Lastly, I have now created a sub Form per Bruce's note as a test and you get a very usable display free of the norm 'Form' stuff that could be confusing.  If you can select a part of your original Form which has a number of Display items and informational stuff such as read-only fields then this area is tailor made for the new Form.

Cheers

Keith

[Bruce]

Hi Keith,

thanks for the feedback.

Just one comment with regard to "the naming of things".

>> This is because this error seems to relate to the number of 'things' in the module and even if a Form, say, has not many fields when you have 10 Forms in a module you can easily have more than the magic number (about 200).

What you call "things" I refer to as "Form fields". Form Fields can be of various types - including buttons, display, procedures, and entry. I think you are referring to "fields" as "entry fields" - but where "entry fields" includes strings, dates, checkboxes, radio and so on. I don't think I have a term for this "group" of field types.

But in essence, you are correct - the limitation is regarding the number of Form Fields (of all types) and is not limited to some subset of form field types.

cheers
Bruce