Some of the feedback we received when we first released StrongTyping was related to the FAST modelling standard. An attraction of the FAST standard is that its structure admits a lot of scope for automated assistance in a way that is more difficult when…
Categories: FAST
Tagged: automation, errors, FAST, input, input sheet, labels, Lyquidity, meta data, metadata, model, modeling, scope, spreadsheet, strong typing, StrongTyping, structure, task pane, types, working
We aim to implement updates to StrongTyping to make it increasingly easy to use. One of the ways has been using the FAST modelling standard – an attraction is that it’s structure admits a lot of scope for automated assistance in a way that…
Categories: Blog
Tagged: automation, errors, FAST, input, input sheet, labels, Lyquidity, meta data, metadata, model, modeling, scope, spreadsheet, strong typing, StrongTyping, structure, task pane, types, working
A type system for Excel needs to emulate some of the features found in languages which support a robust code validation system. The obvious differences between Excel and a formal programming language mean these validation features need to be adapted to work in Excel. For example, in a language based on a list of statements in a text file scopes are defined by the use of start/end delimiter pairs such as ‘{‘ and ‘}’ while Excel is grid of values with no natural scope. A scope might be a column or row of cells but it might be a collection of one or more cell ranges. This article will review the required features and how they can be used in Excel.
