Hi
are populated by the Demand Planner integration business logic. The Demand Planner business logic is written as stored procedures in the Demand Planner database and obtaining the recid through SQL could cause problems that can’t be foreseen beforehand.
** These problems can be taken care of. Not a big deal. There are too many problems with not including this table in AOT for eg. Class DatabaseTransDelete will not touch this table, you cannot make it virtual, i am not sure if one copies the company this table is going to get copied etc etc etc.
With regards to the Demand Planner code, it probably looks different than the rest of the Axapta code due to the fact it reads data from the two external tables.
** Thats just one of the reason, the code also does not strictly ahere to the axapta programming standards.
Regards
Harry
Ps: I think we need to stop this discussion now. You are convinced that demand planner is good, i am convinced it is ugly and I dont think either of us is going to change the position *s*
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Sharing the knowledge on Axapta.
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
