Sorry, have to step in, also...

> Do you test before making a release? 
>
> [ranting about ODBC driver quality]
>
> What's wrong? 

Noone on this list is able to help you, if you
don't give the details. Enable ODBC trace and send
a trace to the list.

Additionally, some people were able to solve similar
bugs by installing SQLStudio on the client machine
(which seems to have different DLLs as the ODBC driver).

> By the way: Installation of the sources + DevTools 
> under W2k isn't funny. The installation-scripts seem 
> to have some bugs with the Registry-communication.

Another glaring example: Don't rant here, give details
(how about an installation transcript??). 

> I think that the DBMS SAPDB won't have a glory future, if 
> such errors still remain in it. It's impossible for me, 
> to tell other people that SAPDB is a real nice DBMS, when 
> they can't connect their damn Windows-Boxes to it. It's
> REALLY impossible.

Your opinion. Many others - including me ARE able to connect
their "damn" windows boxes. And - btw. - their "not-so-damn" 
Linux ones also.

> Please fix those anoying bugs. Maybe it is possible to 
> release beta-versions of the ODBC-driver. The people 
> need them now!

I'm start really to wonder how you are treating COMMERCIAL 
dbms vendors ...

Regards,

Peter

-- 
Peter Schäfer
Dipl.-Ing.(FH)

EADS Radio Communication Systems GmbH & Co. KG
peter DOT schaefer AT sysde DOT eads DOT net

***** NOT SPEAKING FOR MY EMPLOYER *****

Reply via email to