Hi folks, here is a situation we have come across with the Migration wizard for FRx Management reporter for Dynamics GP 2010.
Simply stated the issue is this:
The old FRx databases are Microsoft Office Access databases and so the migration wizard needs certain parts of office connectivity to be able to read and convert the old spec sets into the new FRx Management reporter for Dynamics GP 2010 formats (which are now stored in SQL tables).
FRx Management reporter for Dynamics GP 2010. will only install the components for the operating system it is sat on, so if you are 64bit , it will use the 64 bit Microsoft Office 2010 Access components and if you are 32 bit it will use the 32 bit Microsoft Office 2010 Access components. not a problem so far I hear you cry.
Well now factor in the fact that the new word office template email functionality for Dynamics GP 2010 does not work on the 64 bit version of Microsoft Office 2010 and to get round this a lot of partners are installing the 32 bit version of Microsoft Office 2010 onto 64 bit operating systems in order to use the email functionality in Dynamics GP 2010. Couple this with the fact that if you have FRx Management reporter for Dynamics GP 2010 on a 64 bit operating system it will only use the 64 bit Office components, add the fact that you can not have 64bit office components on a machine that already has 32 bit office components and you have a problem. The Migration wizard will not be able to read the Access database.
So there you have the issue , of course it is easily solved simply do the migration on a machine with all 64 bit components (one you are not intending to use the email functionality from) and you will avoid this issue.
This is definitely a case of forewarned is forearmed.
Showing posts with label FRx. Show all posts
Showing posts with label FRx. Show all posts
Thursday, 17 February 2011
Thursday, 28 January 2010
FRx SP11 and 0 budget amounts
We have now discovered a slight difference between sp11 and sp10 and it revolves around the way they deal with column layouts and the use of the Base-1 feature in the column.
It would appear that if you use the base-1, base-2, base-3 etc. feature in the period column and this takes you into the prior year it will look into the prior year for the budget when the year column is set to base (previously in SP10 it did not do this and the year remained constant).
For example if you run a report for January 2010, the period column is set to base-1 and the year is base. It should go back one period which is December but as the year is set to base you would expect data in the budget column for December 2010. What we are getting is zero.
This is because the base-1 in the period is now changing the year as well and trying to display data from December 2009. As there is no data for December 2009 in this budget (yearly budget) it is returning zero.
The workaround is to hardcode the periods 1 through to 12 rather than using the base-1 functionality. We do have this logged with Microsoft at the moment, however a lot of people have just completed their year ends or are in the process of doing so, which means this issue is likely to be more obvious as people change the years in which they are processing.
It would appear that if you use the base-1, base-2, base-3 etc. feature in the period column and this takes you into the prior year it will look into the prior year for the budget when the year column is set to base (previously in SP10 it did not do this and the year remained constant).
For example if you run a report for January 2010, the period column is set to base-1 and the year is base. It should go back one period which is December but as the year is set to base you would expect data in the budget column for December 2010. What we are getting is zero.
This is because the base-1 in the period is now changing the year as well and trying to display data from December 2009. As there is no data for December 2009 in this budget (yearly budget) it is returning zero.
The workaround is to hardcode the periods 1 through to 12 rather than using the base-1 functionality. We do have this logged with Microsoft at the moment, however a lot of people have just completed their year ends or are in the process of doing so, which means this issue is likely to be more obvious as people change the years in which they are processing.
Friday, 22 January 2010
FRX SP11 we are happy with it now.
The code for FRx sp11 has been re released and we have tested this in house. We are happy to report it does what it says on the packet and we are now happy for our clients to install this service pack.
Monday, 21 December 2009
Bug In FRx SP11 core code (Please do not install)
Service Pack 11 was recently pulled due to a core FRx bug found. The last update from Microsoft's Development is that it should be available for release in 4 weeks.
To roll back to SP9 you can follow KB 861724 "How to remove a Service Pack for FRx". The link is provided below. If you can not access the link please contact helpdesk@touchstone.co.uk
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;861724
To roll back to SP9 you can follow KB 861724 "How to remove a Service Pack for FRx". The link is provided below. If you can not access the link please contact helpdesk@touchstone.co.uk
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;861724
Wednesday, 16 December 2009
FRX and Windows 7
Hi Folks, a quick update to the whole windows 7 compatibility status. FRx 6.7 is now compatible with windows 7 as long as the recently released Service Pack 11 is installed.
for more information on SP11 for FRx 6.7 please contact the helpdesk@touchstone.co.uk
for more information on SP11 for FRx 6.7 please contact the helpdesk@touchstone.co.uk
Subscribe to:
Posts (Atom)
