Nick,

> With this in mind, the phrase "quickly tried to get something to show"

does seem

> a bit unfair, I think I spent more time getting the InstallShield install
> working as I did adding to the driver.

Thanks for the clarifications. In light of what you have said I see that my
understanding was in need of refinement.

So, EasySoft wasn't the action maker to get this driver going, but you
personally. That makes sense and I for one would like to thank you for
making a stand trying to make a case for InterBase. It's just too bad that
for whatever reason your employer didn't take the InterBase possibility
seriously and left you in a position to have to do something about it on
your personal time-frame. And, it's unfortunate that NewCo was only in a
position to act upon what your employer dictated and not you personally.

While this is a noble gesture on your part, you are unfortunately in a
position where you are now possibly at odds with your employer and NewCo,
and yet, you are just trying to make a great thing happen! This industry is
entirely too full of irony!

> I would hope that people who know my work on unixODBC know that my

commitment to

> Open Source development and free ODBC implementation goes beyond this

driver,

> and predates all of NewCo and the current situation.

I bet you are right! But, unfortunately I and many of the current IB folks
aren't aware of this either.

Hopefully you can sell your case to both your employer and Inprise. If that
doesn't work, talk to me and I've got some ideas to share if you are
interested. I've been in shoes similar to yours and I think I have a system
that resolves such a dilemma.

FWIW,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Nick Gorham" <nick@...>
To: <IBDI@egroups.com>
Sent: Monday, September 04, 2000 12:58 PM
Subject: Re: [IBDI] Re: [IB-Architect] EasySoft ODBC Driver & Borland


>
> Jason Wharton wrote:
>
> > >From what I understand, and I surely could be mistaken, the verbal
exchanges
> > were exploratory, not committal. For whatever reason it was deemed
unwise to
> > commit to EasySoft under the terms and timeframe they presented. But
when
> > NewCo shifted to do it themselves EasySoft didn't want to see a market
> > segment gobbled up so they quickly tried to get something to show to
keep
> > their foot in the door. I'm glad they are deciding to commit efforts to
this
> > because the InterBase market can only be benefited by additional ODBC
> > drivers.
> >
>
> Well its hard to comment when people seem to have differing recollections,
there
> is little from being gained in arguing about what happened. But as I was
in the
> meetings with Paul at the time, I came away with the feeling (possibly
> mistaken) that NewCo needed something ASAP, so I started work on the
driver, the
> commitment seemed firm, but then again I am a programmer, and may not
understand
> the subtle issues of sales and marketing :-). After NewCo shifted to do it
them
> self's I was told to stop work on it, and forget it. It was only after the
NewCo
> deal seemed to not be providing a driver, I quietly started work on the
driver
> in my spare time, eventually plucking up courage to mention that it was
almost
> ready to the CEO.
>
> With this in mind, the phrase "quickly tried to get something to show"
does seem
> a bit unfair, I think I spent more time getting the InstallShield install
> working as I did adding to the driver.
>
> There driver is there, people can try it and make up their own minds about
it.
>
>
> --
> Nick Gorham
> "I wish there was a knob on the TV to turn up the intelligence,
> There's a knob called brightness, but it doesn't work."
> - Eugene P. Gallagher
>
>
>
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>