This Article will show you how to convert a C# or VB.NET Date/Time object
into an Internal MultiValue Date. It will show you how to do it using the
ICONV functions, and well as how to generate an Internal Date without
using the ICONV function.
This article will show how to convert a MultiValue (PICK) Internal Date
into a DateTime object that you can use in C# and VB.NET. The article will
cover how use the OCONV statement, as well as, how to generate the DateTime
object without using the OCONV statement.
The attached subroutine will convert a numeric values to their alphabetic
values. The number "4" converts to "four"; "25" converts to twenty five,
etc. There is also an option that will allow you to change a numeric value
into an alphabetic count. For example, 4 converts to "forth", "25" converts
Some of your business processes are complex, some are simple. Let's look at
check writing as an example. This is a really simple process, but you can
run into one small snag.
Reading and writing OS files is very important in the new hybrid systems we
have to write these days. Most of our applications are pretty
self-contained,and don't need to interact with programs or applications
outside the MV environment. But that is slowly changing.
If you are migrating from another MultiValue system to Caché, an
introduction to some key terminology differences would be useful.
The address is a key piece of information in anyone's database, but it can
be extremely hard to validate, and due to free form input, even harder to
Most people in the MultiValue community agree that green-screens are our
death. But you might be caught in the transition from past millennium to
current millennium re-work. Your users are still stuck with antiquated
green-screens but desperately want newer ways of viewing things. Now there
are many fine, modern, MultiValue reporting options out there. But maybe,
for reasons outside of your control, you are not able to purchase them just
yet. Well, take heart, for there is a dirt-simple technique that can provide
your users with at least a smidgeon of what they really want.
These days we have to interact with other systems, which also means
interacting with other dates and times. UTC dates is a common date that we
run into, as well as RFC1123 dates, which are commonly found in web data.
Log onto any MultiValue application that has been in existence for three
years, find a commonly used file, say CUST, and list it's dictionary. What
do you see? Definitions for LNAME, LAST.NAME, L.NAME, LST.NAME, LNAME40,
etc. Upon closer examination you discover that field (attribute) is also
defined as X, XX, PGM030.LNAME.RPT, and on and on. Log on to an application
that has been in use for 30 years and you could find several hundred
dictionary entries for a file with only 20 fields.