This sort of marketing material would have been VERY USEFUL 20 years
ago, to deflect & answer the inevitable "what is Pick?" question

Ohhhh, but wait ... it obviously WAS! Typical of our "Best kept
secret" metality

http://www.youtube.com/watch?v=6ms0yvJAUAk&NR=1

Thanks for making this available Mark .... perhaps you could get
Northgate to add & edit to incorporate the Nothgate story & bring this
up to the current Era

On 2010-10-15 18:51:38 -0400, Ross Ferris <rossf (AT) stamina (DOT) com.au> said:

Yeah. Great vid. The other inevitable question, to which some extent
that video shows near the end, is, "Who uses Pick"?

Does anyone have a comprehensive, current list of today's top companies
using MV databases?

--
Kevin Powick

question has to be asked now - where is it? and where did it go to?

the model pick was didn't perpetuate microsoft tried to launch business
launguages they were heavily adopted for years but they regressed
everything

pick is left with the description 'embedded system' for some reason the
simple model didn't sustain - was it licensing? what was it?

the HELL that microsoft created can still be countered by the pick/RDBMS
model

there are spurious tools about trying to trade on the lost legacy
openinsight cache etc

they are not tools they are nothing

any modern programmer will know that the new data models involve object
orientation and pure language facilities more akin to artificial
intelligence languages

waste your money do it but do not use generational data modelling based
on some idea of pick

use python

ditch SQL ditch whatever crap you are building in openinsight etc

forget it

what can be developed properly in pure pick will ruin your entire life
based on those dead infastructural 'commodities'

dead cults

On Oct 16, 8:48*am, memex <ph0enix... (AT) yahoo (DOT) co.uk> wrote:
Lots of emotion, memex. We are writing new software with Cache' using
the MV data model. The Cache' implementation of the Nelson-Pick model
is the newest one out there. Just to show you I know the jargon (and
not because you need to to write MV in Cache'), we write our metadata
into OO classes that extend a persistent class and provide the DICT
projection, the SQL projection, the Model for use with AJAX, etc all
with the source OO code we write quite simply. The OO objects that are
instances of these classes are records/items in our mv database. We
can have the database version-stamp the records for use with
concurrency handling for web development, for example, and can have
the database autogenerate @IDs where desired. The OO properties are
pick fields/attributes, whether single-valued or "lists" (mv's).

With so many years of successes under its belt, Pick is very useful
and Pick-related tools are very powerful.

It's great that there are many different ways of looking at data. Our
OO persistent classes are written in mvbasic and our web page classes
are written in mvbasic and javascript. MVBASIC has been enhanced for
OO by at least two providers (Cache' and QM) and combined with the mv
query language, it retains its elegance in the combined power and
simplicity of these languages. Pick and MV tools continue to evolve,
even after 45 years since the original development.

LOL. Are you teaching a course or developing workhorse business
applications?

Again, lots of emotion. What's your story?

What happened, memex? I'm collecting stories from the Pick world and
it sounds like you have one. Can you give me some hints at least?

Living solutions. --dawn

On Oct 15, 7:57*pm, Kevin Powick <nos... (AT) spamless (DOT) com> wrote:
Ahhh the perpetual question Kevin. The list that all OEMs and
software vendors would like to get, but would never like to share.
It's up to the end-users to create it. Want to help me get one
started?

Will