Hello Jazib Things to consider: Additional info in EmplTable 1. If the addtional attributes are 1 occurence only, ie like Birthdate. (just an example) You cant have multiple birth dates per employee. Then i would add these to the EmplTable These are some additional arguments a. Db remains consistent and get updated through standard routines on subsequent releases. b. Code change is minimal for insert/update/delete. c. New code written is also dependent on the business logic being offered for these new attributes. 2. If the additional attributes are multiple occurences, say Children Details with birthdates.(Just an example) I could have multiple records or 1 record. In this case i would add an additional table. In some cases based on the attributes, look for another suitable table in Axapta that has a parent/child relationship and add the additional attributes there. hope this helps Thanks Rajesh
----- Original Message ---- From: jazib.abdulah <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, May 7, 2008 9:11:35 AM Subject: [development-axapta] Need some design guidance Hi everybody I have to develop a small customization in Axapta which will help user maintain some more information related to Employees which is presently not avaialable in EmplTable. What should I do? Should I make changes in EmplTable or Should I make another table of my own which will contain extra info and make some kind of one to one relationship with EmplTable Please keep in mind that this new Information is direct information of every employee and does not make Parent-child relationship with EmplTable and also I will have to add some methods in EmplTable that will give user some extra options related to Employee. Thanks very much in advance. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ [Non-text portions of this message have been removed]
