MBS has clearly stated that the current generation products will be developed and supported until at least 2013. The current generation of Great Plains is based on Dexterity. Dexterity is still the tool of choice for tight integrations. VBA can only see user interface events and cannot trigger on procedure, function or database events.
If you want to change or add to the functionality of Great Plains you will need to have Dexterity as one of the tools available to you. So far, the only areas that I have found VBA has an advantage on Dex is triggering in reports and being able to change 3rd party product windows.
Dexterity has "at least" nine years of life ahead of it.... and that is a really long time in the IT world.
There are no examples specific to this case in any documentation. Once you know how to work with Dex, you can log the scripts and find the place where the ranges are being set. However, in this case it does help to have access to the source code.
The triggers are needed on the following form procedures:
SetRangeDocTypeForCorpCustByDocNum of form rmOpen
inout rmOpenState Me;
in 'Corporate Customer Number' sCorpCustNum;
in 'RM Document Type-All' nStartDocType;
in 'RM Document Type-All' nEndDocType;
SetRangeDocTypeForCustNumByDocNum of form rmOpen
inout rmOpenState Me;
in 'Customer Number' sCustNum;
in 'RM Document Type-All' nStartDocType;
in 'RM Document Type-All' nEndDocType;
You will need to change the value of Me:Index to the index you are using and set the new range on table(Me:'Table Reference').
Look at the RM_OPENDebitCopy table for the key information.
Does that help?
David Musgrave [MSFT]
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.
This posting is provided "AS IS" with no warranties,
and confers no rights.