Hi, Then go back to the drawing table and design what you really want. But first start by reading this: http://www.csci.csusb.edu/dick/samples/uml0.html
In practise I would say: functionality is wrapped in classes. Classes can be run from everywhere, also from a GUI... In the end it all depends on the time you have and budget you have to work with. In other words: the relation you are missing, can be explained by finding out what your interpretation is of an objects responsibility. There are a lot of books to find, ie: "from structured to Object-Oriented programming" - J.J. van Amstel, Academic Service, ISBN 9062335276 Succes, /b //*** the Real B **// gollywogman schreef: > > Greetings Everyone > > I was just wondering, has anyone got any suggestions on how to create > both forms AND classes while maintaining proper object orientated > prinicples. > I am busy creating a form that creates a new record of some sort, and i > would like to return the id of the new record. Does this mean that i > need to instantiate the form, (which can't really be done in Dynamics), > or must I instantiate the record? I'm just struggling to see the > relationship between data, classes and forms in an object orientated > way. I want to use OO as much as possible (including extension and > polymorphism), so that my code is reusable, abstracted and component > based. I want to steer clear of procedural programming. > Any help would be great! > > Thanks, > b > > > Messages in this topic > <http://groups.yahoo.com/group/development-axapta/message/15337;_ylc=X3oDMTM1MHY1c3FmBF9TAzk3MzU5NzE0BGdycElkAzUxNDQ5NARncnBzcElkAzE3MDUwMDY3NjQEbXNnSWQDMTUzMzcEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMTcwNzYyNTYyBHRwY0lkAzE1MzM3> > (1) > <http://groups.yahoo.com/group/development-axapta/post;_ylc=X3oDMTJwbXBzNGs2BF9TAzk3MzU5NzE0BGdycElkAzUxNDQ5NARncnBzcElkAzE3MDUwMDY3NjQEbXNnSWQDMTUzMzcEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMTcwNzYyNTYy?act=reply&messageNum=15337>
