December 21, 2004 7:44 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] modern day programming (was:
Intersystems)
Ostrander, Terry L. wrote:
>Proof is in the pudding.
I totally agree. Concrete examples and comparisons can be quite
illuminating.
>I created the n
or Live CDs work well)
> Universal External access to data and routines (hmmm...)
/David.
And for those interested in that CRM:
http://www.sugarcrm.com/home/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Walton, Edward NMN(WSH)
Sent: Wednesday, Decem
---
From: David Sommers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 22, 2004 12:22 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] modern day programming (was: Intersystems)
I'd honestly say that the approach to querying data out of M and using it
wi
Encoding.ASCII.GetBytes(plainText));
> >
> > Want that in Base64?
> >
> > string s64 = Convert.ToBase64String(cb);
> >
> > I have similar functions for VB6 but I had to write the libraries
> > that
> > make it work. So it really is your "skillset"
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg
Woodhouse
Sent: Wednesday, December 22, 2004 3:58 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] modern day programming (was:
Intersystems)
In fact, VistA does supply some u
So it really is your "skillset" and your "bag of
> tricks"
> but the more flexible you are to allow external tools to work, the
> more
> likely a system will be adopted.
>
> Then there are web services... but that's another thread... :)
>
> /Da
[mailto:[EMAIL PROTECTED] On Behalf Of Greg
Woodhouse
Sent: Wednesday, December 22, 2004 12:52 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] modern day programming (was:
Intersystems)
I'm sure that's a big part of it. Though every product out there seems
to
I'm sure that's a big part of it. Though every product out there seems
to have its own flavor of SQL, using a relational database does offer a
common model, and I suppose knowledge of MySQL (say), is more
"transferable" to Oracle than it is to Fileman -- though, in fact, I
think Fileman is much mor
t; horror stories but [to me] it seems to be a faster route. Question
> isn't why should I use straight M but why not use SQL connections?
>
> /David.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jim
> Self
> Sent:
to me
to offer some important long term and short term advantages.
>
>
>/David.
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Jim
>Self
>Sent: Tuesday, December 21, 2004 7:44 PM
>To: hardhats-members@lists.sourceforge.net
&
x27;t why should I use straight M but why not use SQL connections?
/David.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim
Self
Sent: Tuesday, December 21, 2004 7:44 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] moder
Ostrander, Terry L. wrote:
>Proof is in the pudding.
I totally agree. Concrete examples and comparisons can be quite illuminating.
>I created the necessary Cache' objects to
>emulate a VistA system and now I am able to perform ADHOC queries and
>write programs using modern day programming langua
12 matches
Mail list logo
