Re: SAPDB not competitive due to neglect of Win32 drivers

>>That still true, but it Mono might become a good choice for cross
>>platform development too, although that might take some years.
> 
> Well, C# and .Net is going to be windows only and almost
> exclusively microsoft backed, so if you think you are getting cross
> platform capabilities like Java or Perl, think again, it's going to be
> more like the cross platform capabilities of C when you use a lot of
> binary only liberaries.

It's a bit OT but you just said .NET was "invented" my Microsoft, you 
didn't tell anything what you expect for Mono's future. I hope it 
odesn't get forbidden due to any software patents.
BTW: ODBC was invented my MS to (i don't know for sure, but i'm about 
99% sure), and it's going to get popular for UNIX too.

>>Well, you're using ODBC, and i guess Stephen can't use ODBC any more
>>since it is poorly supported by .NET ...
> 
> Then maybe he shouldn't use .NET?

What an arrogant position.

>>>Why can't a C# driver link to the ODBC driver?
>>
>>Surely he could, but you'd reinvent the wheel because you're just
>>writing yet another ODBC bridge.
> 
> So if an ODBC bridge already exists, then what is he missing?

Would you use the JDBC-ODBC bridge? i guess no. You would expect a good 
JDBC driver and fortunately we have such 100% Java driver for SAPDB.
Without it, i wouldn't have chosen SAPDB for my work, since a bridges 
are often faulty and unreliable.

> Writing a new .NET-only sapdb client does not make it better, the solution
> is to use the ODBC interface and if it turns out to be lacking, improve
> it.

Well, we can't influence the ODBC API itself, just solve bugs within 
SAPDB's ODBC driver. In addition you'll have to fight with the birdge's 
bugs.

> I've heard mumblings of a new, modern ODBC interface being written for SAP
> DB, so maybe that's the answer; wait a while and see if a better driver
> should pop up.

What the hell is a "modern ODBC interface" ?
Will the SAPDB ODBC driver support a higher version of ODBC?