Board index » delphi » Sybase Adaptive Server Anywhere and SQLLinks / Explorer

Sybase Adaptive Server Anywhere and SQLLinks / Explorer

Trying to use the ASE driver with ASA is pissing into the wind. If
you're using ASA6, you must use its ODBC interface.

If the BDE is too slow, and you can't improve performance by adjusting
your transactions (e.g. explicit commit every 100 posts), try a
third-party ODBC interface such as ODBC 98 or ODBC Express
(http://www.odbc98.com, http://www.odbcexpress.com). You might also look
at news://forums.sybase.com/sybase.public.sqlanywhere.general for
performance tips.

  Richard

Quote
Karlheinz Spaeth wrote:

> This configuration does *nearly* work.
> There are however some misspelled SQL statements from SQL Explorer, that
> cannot by understood by ASA. It seems to select a field "allownulls" that
> should be "allowsnulls".
> If I change the view on the server to reflect this fact, I get another
> errors. Explorer does not use quotes (") for the fieldnames. This does not
> work for field names like "first" or "variable" - since these are reserved
> words.

> Browsing through the newsgroups there seem to be a reasonable demand for a
> link to this database. It should be easy to fix these "bugs" in SQLLinks to
> get a new kind of driver.

> Other reasons:

> ADO/OLEDB native drivers not available (for now)
> ADO/OLEDB/ODBC does not work at most
> 3rd party drivers have problems (TITAN)
> ODBC/BDE is much too slow for batch operations.

> Using ASA 6.03, D5 Enterprise, NT4

> --
> Karlheinz Spaeth

 

Re:Sybase Adaptive Server Anywhere and SQLLinks / Explorer


This configuration does *nearly* work.
There are however some misspelled SQL statements from SQL Explorer, that
cannot by understood by ASA. It seems to select a field "allownulls" that
should be "allowsnulls".
If I change the view on the server to reflect this fact, I get another
errors. Explorer does not use quotes (") for the fieldnames. This does not
work for field names like "first" or "variable" - since these are reserved
words.

Browsing through the newsgroups there seem to be a reasonable demand for a
link to this database. It should be easy to fix these "bugs" in SQLLinks to
get a new kind of driver.

Other reasons:

ADO/OLEDB native drivers not available (for now)
ADO/OLEDB/ODBC does not work at most
3rd party drivers have problems (TITAN)
ODBC/BDE is much too slow for batch operations.

Using ASA 6.03, D5 Enterprise, NT4

--
Karlheinz Spaeth

Other Threads