MoneyWorks support
Persistent Data and DevKeys
In MoneyWorks 7 we introduced a new internal data table called "User2", specifically so that mwScripts and external plug-ins can store their own persistent data in a MoneyWorks database. However with diverse scripts each storing their own data, there is … Continue reading
Schema
You can obtain the full MoneyWorks database schema by exporting "xmlschema" to a file. E.g. tell application "MoneyWorks Gold" to export "xmlschema" into POSIX file "/schema.xml" Note that text field usable sizes are general one byte less than the size … Continue reading
User2
Version 7 contains a new script-accessible table for developers' use. It behaves rather like the existing user file except for having a much larger primary key (27 chars) and also a numeric "developer key" intended to prevent data collisions between … Continue reading
Privilege encoding
MoneyWorks 6 and earlier encodes privileges as a string where each privilege is represented by a character in the range 32-130. This is kind of wasteful and also unfortunate, because the last 3 codes are not valid utf-8. Making them … Continue reading
Unicode
MoneyWorks 7 stores all text internally using the Unicode UTF-8 encoding. This allows proper compatibility between Mac and Windows for Roman text outside the ASCII range (which previously was not translated between MacRoman and WinLatin), and also allows for input … Continue reading
Crash recovery
After a crash or power loss, Moneyworks will normally recover unsaved changes from the session file the next time a document is opened. There is a confirmation UI if you open the file directly. If the file is opened in … Continue reading
Stickies
I shouldn't tell you this, because the knowledge is open to extreme abuse by the irresponsible... Displaying sticky notes in a list column This is for transactions (directly owned sticky notes) Find("Stickies.Message", "FileNum=5 and OwnerSeq="+SequenceNumber, 9) File number 5 is … Continue reading
Reference number allocation
We sometimes get queries about gaps in reference number sequences. Why would MoneyWorks be so dumb as to skip reference numbers? In fact, reference number allocation is not that trivial. Consider the situation where you open 5 new invoice windows. … Continue reading
XML data exchange
MoneyWorks 6.1 and later supports import and export of xml-formatted data. This removes the need to preconfigure an import map when building automated importing scripts (although you will still need to understand import maps). XML is the only import format … Continue reading
Relational Find for arbitrary link fields
When you do a relational find for anything that does not have a link that shows up in the Find Related dialog box, then you must explicitly provide the link fields. A good example of this is when finding Ledger … Continue reading