Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Dexterity Problem
- Thread starter 6318285
- Start date
winthropdc
Programmer
You will need to give us some more details of what you are doing. Do you get any error messages?
I would also suggest reading the Integration Guide manual that comes with Dexterity, or even better attending a Dexterity class.
There are some rules you must understand about dexterity development for integrating applications.
1) You start with a copy of the Dynamics.dic. Make your changes and additions and then use Dexterity utilities to create a chunk file.
2) You must obtain a product id for your chunk file from MBS.
3) You must never deploy a modified Dynamics.dic, you must always deploy your chunk.
4) You must not change a table definition for a GP table.
5) You can modify existing forms and reports and transfer them as alternate forms and reports in your chunk.
6) Never delete any field from an modified form or report.
7) Never try to edit scripts for existing fields, you will see that there is no source and if you try saving it will corrupt the existing executable code.
8) Use triggers to add your code to existing windows. I recommend using triggers for fields you have added to alternate windows too.
9) Don't forget to change security for access to alternate forms and reports.
10) Attend a Dexterity class and obtain Dexterity CSE (Certified Software Engineer) status as soon as you can.
Hope this helps.
David Musgrave
Senior Development Consultant
MBS Services - Asia Pacific
Microsoft Business Solutions
Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
I would also suggest reading the Integration Guide manual that comes with Dexterity, or even better attending a Dexterity class.
There are some rules you must understand about dexterity development for integrating applications.
1) You start with a copy of the Dynamics.dic. Make your changes and additions and then use Dexterity utilities to create a chunk file.
2) You must obtain a product id for your chunk file from MBS.
3) You must never deploy a modified Dynamics.dic, you must always deploy your chunk.
4) You must not change a table definition for a GP table.
5) You can modify existing forms and reports and transfer them as alternate forms and reports in your chunk.
6) Never delete any field from an modified form or report.
7) Never try to edit scripts for existing fields, you will see that there is no source and if you try saving it will corrupt the existing executable code.
8) Use triggers to add your code to existing windows. I recommend using triggers for fields you have added to alternate windows too.
9) Don't forget to change security for access to alternate forms and reports.
10) Attend a Dexterity class and obtain Dexterity CSE (Certified Software Engineer) status as soon as you can.
Hope this helps.
David Musgrave
Senior Development Consultant
MBS Services - Asia Pacific
Microsoft Business Solutions
Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
- Status
Similar threads
- Locked
- Question
- Locked
- Question