One of the tasks that was like headch for me was to enable the created by and modifed by in sepicfic group of tables , which is a very important requirment in every succefull implemetation
so that i invented a solution for these task , the following job will enable any one to track the changes in the data by enable created by/created date time and modified by / modified date time property in each Parameter and Group Table type which will allow you to catch any one trying to mess up the appication
static void EnableTableProperty(Args _args)
#AOT Name name;
treeNode = TreeNode::findNode(#TablesPath);
treeNode = treeNode.AOTfirstChild();
name = treeNode.AOTname();
sysDictTable = SysDictTable::newTableId(treeNode.applObjectId());
if ((sysDictTable.tableGroup() == tableGroup::Parameter ||
sysDictTable.tableGroup() == tableGroup::Group) &&
node = SysDictTable.treeNode();
node = null;
Twenty Must-Know Tips Before ERP Implementation
- ERP is about your business, not the technology.
- ERP initiatives are very challenging.
- Selecting the right software is the first step in a successful ERP implementation.
- No ERP software is perfect. All have their strengths, weaknesses and tradeoffs.
- A business blueprint is the second step to an effective ERP implementation.
- Business process re-engineering should happen before – not after – you implement your ERP software.
- ERP software best practices and pre-configured solutions do not solve all of the challenges of ERP.
- SaaS ERP won’t eliminate all of your risks either.
- Your project will fail without adequate organizational change management.
- Executive buy-in and support is critical to ERP success.
- The “A-Team” is critical to ERP success.
- There is no “one size fits all” ERP strategy.
- If your operations and your ERP system are misaligned, it’s probably not the software’s fault.
- Expectations are high, but most ERP implementations don’t properly define the “finish line.”
- Organizations that strive for “no customization” often end up doing it anyway.
- You don’t have to implement ERP all at once.
- In addition to planning, implementation is also about execution.
- If you don’t measure it, you won’t achieve it.
- It is important to recognize the “canary in the coal mine” or signs that your implementation may be in trouble.
- ERP success and benefits realization is largely determined before the implementation starts.
- With the language constructs you’ve learned so far, you can build powerful objects of many different types. You do this mostly by declaring classes that encapsulate the behavior you want and then creating instances of those classes.
- All the types used in the class declarations so far have been specific types—either programmer defined or supplied by the language or the BCL. There are times, however, when a class would be more useful if you could “distill” or “refactor” out its actions and apply them not just to the data types for which they are coded but for other types as well.
- Generics allow you to do just that. You can refactor your code and add an additional layer of abstraction so that, for certain kinds of code, the data types are not hard-coded. This is particularly designed for cases in which there are multiple sections of code performing the same instructions, but on different data types.
- So that i think it is time to learn more about generics …. the following artical will talk about generics and catch the headlines that will help you invest generics in your code .. leaving you with the artical .. hoping to be helpful
This Article Demonstrates how to use MultiThreading in c# programming , and the new updates in .Net FrameWork 2.0 SDK, and Discuss many problems and illustrates how to solve it such as Concurrency, so lets see what this subject talks about
Visual CSharp® 2005 How to Program, 2nd Ed – [Prentice Hall]
Pro-C# 2008-and-the-NET-3.5-Platform 4th Edition Apress
For more information