>Didn't some clever person devise a method to stuff several forms (individual SCX's) into a single formset SCX? I have some situations where I would prefer to use this utililty rather than saving my forms as classes and dumping them into a formset. In general, I've found this method to be cumbersome because most of these forms are of the "use once" variety, and I consequently find myself needing to frequently modify the base class. This is a nuisance because you cannot edit the base form and the formset at the same time (i.e., Cannot modify a class that is in use). So I would prefer to use a forms-to-formset builder utility thingy. How about it?
>Thanks!
we do a fair amount of work on edi and electronic medical claim files which are in the old cobol overlay structure. ie 320 character long records with the first 3 characters in each line/record defining a different record structure. there are various sequence requirements and the codes defy proper indexing. we created a parent class (wrapper) which contains subclasses of a screen per record type. The navigation tools are straight forward. Move forward a record and see from the first 3 characters which screen class needs to be visible or possibly instantiated if we have not seen it b4. the data sources are properties of other classes which are also a class per record type. it sounds cumbersome but in reality it works quite well and is easy to maintain. the next step will be to set the whole thing up in a data dictionary. VFP6 promises the ability to add a property to an instance of a class on the fly. that will make things even easier. hth b