The record generator is not necessarily appropriate for every record type.
You could modify the code generated if you need to. Just be careful not to break the other records. If you wish to do a one off generation then what you suggest will work. You might be able to use XML entities to include your common code. You will get lots of duplicated generated code but since it's generated this is not too evil. Even with this case however you probably want a common interface yes? If so you might need to tweak the generator slightly to allow you to specify a particular interface. The record generator is a hammer but you might have a screw there instead of a nail. Regards, Glen PS: Sorry it took a while to answer you. > I'm working on margins and need to create records for them. They all have > the same structure except the sid is different. I was wanting to create a > MarginRecord using the record generator and then sub-class the actual margin > classes. This does not work because of the requirement of needing a sid. > Is there a way to make it work nicely without a sid or do I need to generate > the class, clean it up, and destroy the record file (so it does not get > overridden)? Basically, I'm wanting to stay along the lines that the rest > of the code follows. > > Shawn > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
