Hi Joe,
 
So you're saying we're dammed if they do (write it themselves) and we're
dammed if they don't?  <big grin!>
 
At any rate, although it may not have been clear in my original posting, my
concern is not with whether HP writes it or OEM's it.  My concern is the
length of time that it is taking HP to resolve the problem with what I would
consider to be such a key piece of software.  If they do deliver by the end
of the year, then that means that it will have taken them a full year to
provide a solution.  To me, this seems extreme.  Keep in mind here that I am
not just bemoaning the lack of a 32-bit client.  My bigger problem lies with
the fact that the current 16-bit client has some serious bugs which are
preventing us from moving forward in a timely manner with our client/server
development.  If the HP3000 is to be a player in this arena, then a solid,
functional ODBC driver is a must!
 
Gary
 
>>> Geiser, Joe says: <[log in to unmask]> 09/06/96 08:22am >>>
Gary,
 
You bring up some nice points - but my experience with HP and software for
the PC (which goes back to 1986) has always shown the following:
 
1.  If they OEM it, they're always - not sometimes, but *always* at least
one to two versions behind the original product...
 
2.  If they wrote it, it's underlying technology is current or cutting edge
for version 1.0, then it lags behind from there on...
 
[snip]