RE: Import from Sybase SQL Anywhere 9

Hello Mark,

I found similar issue reported and it seems to be caused by olddb driver
from sybase.

I've been reading the .NET connectivity papers on ianywhere.com and
searching the Sybase newsgroups for information on configuring the Sybase
OLEDB driver. I noticed almost all of the newsgroups support for
configuring the SQL Anywhere OLEDB providers was provided by the
ianywhere.com support staff.

Most of these technical papers and discussion contain the user name and
password in the Provider String parameter.

Migrating a Microsoft Access Application into a .NET Solution that Uses SQL
Anywhere
<http://www.ianywhere.com/developer/sql_anywhere_developer_corner/migrate_ac
cess.html>

Provider=ASAProv.90;User ID=uid Password=pwd

http://www.ianywhere.com/developer

About the .NET Data Provider for SQL Anywhere Studio
-------------------------------------------------------
SQL Anywhere's strong tradition of the .NET Framework support in its data
management and data synchronization technologies is further enhanced with
its newly
announced support for ADO.NET 2.0 and integration with Visual Studio 2005.
The new ADO.NET 2.0 provider allows native access to SQL Anywhere data
management
technology. Integration features with Visual Studio 2005 will make it easy
for developers to build data-driven .NET application for frontline
environments.

You may want to contact their support to see if there is any updated driver
to work around this issue.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================



This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages

  • Re: Dateadd in SQL statement not working
    ... Omigod, I thought you said you were using SQL Server, which is what my ... version of SQL used by Jet, which is the database usually used by Access): ... But my confusion is not totally resolved: Why are you using a Sybase ODBC ... driver to connect to either a Jet or a SQL Server database? ...
    (microsoft.public.inetserver.asp.general)
  • Re: read/write/create dbf file
    ... What driver should I use for support 'dbf' files? ... I was trying Microsoft.Jet.OLEDB.4.0 but it doesn't support 64 bit computer. ... DBF to SQL Converter allows you to convert your dbf files to SQL script. ...
    (microsoft.public.dotnet.general)
  • Re: Error on SSIS PrimeOutput()
    ... We are using the ProvideX ODBC 3.31 driver and it works perfectly under SQL ... > If you do not use SAP provider, it is more like a driver related issue. ... > that you open a Support incident with Microsoft Customer Support Services ...
    (microsoft.public.sqlserver.dts)
  • Re: Sybase to Access
    ... would be willing to accept SQL 2005 _CRAP_ that is built into VB 2005. ... supported on TRANSMETA, ... I've had apps with an Access database that was 500MB, ... Access could use link tables to link to Sybase perhaps and ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Sybase to Access
    ... I've had Access apps with 25 mb of data that can't support a half dozen ... MDB shouldn't be used for a single user nor a single record. ... If MS had a decade-long policy of preaching SQL over MDB then _MAYBE_ I ... Access could use link tables to link to Sybase perhaps and give ...
    (microsoft.public.dotnet.languages.vb)
Loading