What are flavors of PICK Basic?

#11

"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote

Quote:

"dawn" wrote:
Is there any chance we could get at least a standard means of
specifying an MV data source to products out there that will be able to
work with XML data sources?

Once again the answer to your question is .NET, which is heavily built
around XML, and the ideal tool to facilitate the process for most MV
DBMS environments on any OS is mv.NET:
- You can import MV data into an ADO.NET dataset and generate an XML
schema for use by other products.
- You can import XML Data into an ADO.NET dataset using a provided
schema. From there you can exchange data directly with MV.

What we lack, which some lucky entrepreneur will one day surely
provide, is a product/application which magically does this, so that
people focus on the XML and not the .NET or connectivity tools.

I keep tellin ya Dawn - the answers are there, you just need to grab
the brass ring to win your prize.

T

What about BRIZ I am only testinfg the waters but it seems to be a lot

further down the track that any others,
Peter McMurray

#12

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

Quote:

"louiebergsagel (AT) yahoo (DOT) com" <louiebergsagel (AT) gmail (DOT) com> wrote in message
news:1147036710.800045.120060 (AT) j33g2000cwa (DOT) googlegroups.com...
Yes, you can pick which "flavor" you want to use in UniVerse.

For instance, the last company I worked for used the "Prime
Information" flavor, which I much prefer.

My current company uses the "Pick" flavor.

Although why they can't all be incorporated into one is beyond me. Most
commands already have 3 valid syntax choices, it seems like it would be
fairly simple to allow them all. Why should I be forced to type
ID-SUPP on one version, when I learned "ID.SUP" as a "child"? Why
should I be forced to use <1> in a locate statement on one version and
not on another? Sheesh!

And why doesn't UniData have a DICT.DICT, and why don't they have field
names in their dictionaries by default?

And why does one version allow three-dot "..." wildcard expressions and
another require square brackets? Isn't the world all about inclusion
these days?

Sometimes I am just flabbergasted, and often dismayed.

-- Louie Bergsagel, 2006 President, Seattle Area Pick User's Group
(SAPUG)

In a word: competition. Why would you ever buy one version of anything
over another? Why Ford or Chevy or Dodge?

Once they were all the same, when there was just Pick. But each new
vendor had to add something to make it unique and make you want their
version.

Instead of decrying diversity, we should be embrassing it.

Mark Brown

Are the wonders of the English Language when misspelt. Was that

"embarassing" or "embracing" it?

.
Peter Mcmurray

#13

Mark

Agreed about embracing the standards and then extending...

but.. surely if UniVerse has compatibility with other flavours, surely it
would be simple for them to support both flavours at the same time unless
there is a conflict between their syntax. This means that two people who
both use UniVerse are actually using different systems! Surely this
fragments the UniVerse marketplace up and makes employment of new staff to
run with UniVerse more difficult ? This can't be in IBM's best
interest!!!!

Regards
Simon

--
================================
Simon Verona
Dealer Management Service Ltd
Stewart House
Centurion Business Park
Julian Way
Sheffield
S9 1GD

Tel: 0870 080 2300
Fax: 0870 735 0011

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

Quote:

"louiebergsagel (AT) yahoo (DOT) com" <louiebergsagel (AT) gmail (DOT) com> wrote in message
news:1147036710.800045.120060 (AT) j33g2000cwa (DOT) googlegroups.com...
Yes, you can pick which "flavor" you want to use in UniVerse.

For instance, the last company I worked for used the "Prime
Information" flavor, which I much prefer.

My current company uses the "Pick" flavor.

Although why they can't all be incorporated into one is beyond me. Most
commands already have 3 valid syntax choices, it seems like it would be
fairly simple to allow them all. Why should I be forced to type
ID-SUPP on one version, when I learned "ID.SUP" as a "child"? Why
should I be forced to use <1> in a locate statement on one version and
not on another? Sheesh!

And why doesn't UniData have a DICT.DICT, and why don't they have field
names in their dictionaries by default?

And why does one version allow three-dot "..." wildcard expressions and
another require square brackets? Isn't the world all about inclusion
these days?

Sometimes I am just flabbergasted, and often dismayed.

-- Louie Bergsagel, 2006 President, Seattle Area Pick User's Group
(SAPUG)

In a word: competition. Why would you ever buy one version of anything
over another? Why Ford or Chevy or Dodge?

Once they were all the same, when there was just Pick. But each new
vendor had to add something to make it unique and make you want their
version.

Instead of decrying diversity, we should be embrassing it.

Mark Brown

#14

Many competing companies follow standards.
There is no reason why there can't be a multivalue (syntax) standard.
Compete with features, not different spellings of the same functon.

-- Louie

#15

On the Universe and Unidata flavor options, lets not also forget the
compilation $OPTIONS which allows you to set the BASIC flavor for
compilation even though the account flavor, this negates
incompatibility issues because you can always code in the flavor of
your choice.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

What are flavors of PICK Basic?

comp.databases.pick comp.databases.pick

Re: What are flavors of PICK Basic? - 05-08-2006 , 03:14 AM

Re: What are flavors of PICK Basic? - 05-08-2006 , 03:17 AM

Re: What are flavors of PICK Basic? - 05-08-2006 , 05:09 AM

Re: What are flavors of PICK Basic? - 05-09-2006 , 12:51 AM

Re: What are flavors of PICK Basic? - 05-14-2006 , 10:39 PM