| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
OK - here's one for the engineers who do it at code level with BLISS: For ALL-IN-1 V2.4 (and V3.0 if its different), what are the *correct* FMS form set limitations for # of total fields, # of linked forms, and total record size? The V3.0 books still say 31 or 32 forms and 255 Fields MAXIMUM. Today I read on DECUServe that the *old* limits were 255 FORMS(!) and a max record length of all fields together not to exceed 32K. I am coding an application that has over 400 fields. I need to know EXACTLY what the current (2.4 & 3.0) limitations are. finally, are these limits set by FMS itself, or some constraint in A1? Running out of time of this project - Al
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1266.1 | It's worked out slightly differently in the code | IOSG::HULIN | Ian Hulin, IOSG: REO, DTN 830-6141 | Fri Oct 30 1992 17:58 | 25 |
Al,
This is just to confirm the phone call I gave you back in August. I'm
still catching up on this conference now I'm back working back on
ALL-IN-1 IOS ("...gee but it's great to be back home...").
The FLC code has a limit, but it's not the number of fields in the
form set, it's the maximum underlying size of an RMS record containing
all the FMS fields in all the component pages in the form-set. The
magic number for V3.0 is 32229.
So to find out how many fields you can fit on, "all" you have to do is
add up the length of all the fields, and see if it's less than 32229
bytes.
I think the number 255 has arisen apocryphally because it's sort of
safe, easy to rememember and won't break unless you've got a load of
mega-big fields in your form-set.
Hope this is useful.
Cheers,
Ian (an OA$ALPHA_PORTER)
| |||||