Archive for the ‘Accessibility’ Category

David MeegoA new feature to the Support Debugging Tool for Microsoft Dynamics GP build 11 is the support for the rw_ReportStart, rw_ReportEnd, rw_TableHeaderString, rw_TableHeaderCurrency, rw_TableLineString, and rw_TableLineCurrency report writer user defined functions.

The Knowledge Base (KB) article below explains how a third party developer can add triggers to the place holder RW functions in the core Dynamics.dic.  Then when they are used as User Defined functions from a calculated field in Report Writer, the developer can read the parameters passed in and return the desired data from their data.  This allows simple integration of data from a third party dictionary back into a modified report from any product.

Useful functions for developers to use instead of creating alternate reports in Microsoft Dynamics GP (KB 888884)  Secure Link

The first two parameters for all 6 of the report writer functions is a Product or Dictionary ID and a Report Name.  If you set the Dictionary ID to 5261 which is the Support Debugging Tool’s ID and the Report Name to the name of a Script ID from the Runtime Execute window, you can run scripts to capture data from calculated, legends, report, or table fields and log them using the MBS_Auto_Log Helper function.



Read Full Post »

If you’re an Opera user, the Norwegian browser has upgraded to version 9.62 to plug two potential security breaches that could be used to execute arbitrary code. (more…)

Read Full Post »

Classic 404 error pages are prone to being relatively useless. Whilst a well designed page can provide a means to find what they are looking for, wouldn’t it be great if you could find out more about what went wrong? This tutorial will show you how simple it is to have an explanatory email sent to you whenever a visitor hits a 404 page. (more…)

Read Full Post »

1. Validate your XHTML and CSS

Validating your code can often lead you to discover problems which you didn’t notice before. Things such as unclosed and mis-typed tags which look fine in your browser, but could cause problems when viewed by others. The main two tools you need to use are a XHTML Validator and a CSS Validator. (more…)

Read Full Post »

The basics

The idea behind web accessibility is ensuring that everyone, regardless of their platform, browser or personal situation can easily browse your website. This often (but not always) involves the need for the following things:


  • High contrast versions of your pages being available
  • Alternate text being placed on links and images
  • Links being appropriately named, for those with text-to-speech browsers
  • Testing your site without Javascript and CSS turned on
  • Providing appropriate META data (more…)

Read Full Post »