ASA v15 Visual Studio connectivity

[DreamU]

I have just installed Visual Studio v9.0 and am accessing
ASA v15 using ODBC. The problem is I only get to see a list
of views, from which I have accessed the database. But, no
other objects are displayed, in particular, tables! I am
logging in through ODBC as 'sa'.

Any reason why I cannot see tables in the Visual Studio Data
Source Configuration Wizard? Should I be using OLEDB
instead?

[DreamU]

typo: should be ASE v15.

[Paul Vero [Sybase]]

Hi -

What version driver - this was a known issue and should be resolved.
You should get the SDK 15.0 ESD#18 version (15.0.0.350)
and when you get that install the metadta sprocs - run teh
install_odbc_sprocs
to the ASE you're working with and the appropriate script will be installed.

-Paul

<DreamU> wrote in message news:4a54e583.5d1...@sybase.com...

[jimthomas]

Thanks Paul. I mentioned your suggestion to the DBA here but
he went in another direction which was to use OLEDB instead
of ODBC. That cleared the issue and I could see all tables.

However, I have another connectivity issue with Visual
Studio. As a simple start I just created a datasource to an
ASE 15 table of States (no more than a couple hundred rows).
In Visual Studio I can use the Preview screen to see the
list of States.

I then simple dropped a datagridview on the form, told the
datagridview that the data was coming from that States tbl
and ran the program. Note that I have written no code - all
is drag-and-drop.

The program times out after 30 secs with an
"AccessViolationException was unhandled" followed by
"OLEDBException was unhandled". The actual line of C# code
was:

this.memberTableAdapter.Fill(this.dataSet1.member);

which as I mentioned was generated by Visual Studio.

Here is my connection string as generated by VS (password
x'd out):

connectionString="Provider=ASEOLEDB.1;Data
Source=sun1,9017;Persist Security
Info=True;Password=xxxxxxx;User ID=sa;Initial Catalog=anami"

And here is the text of the exception message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.SEHException: External
component has thrown an exception.
at
System.Data.Common.UnsafeNativeMethods.IRowset.GetNextRows(IntPtr
hChapter, IntPtr lRowsOffset, IntPtr cRows, IntPtr&
pcRowsObtained, IntPtr& pprghRows)
at System.Data.OleDb.OleDbDataReader.GetRowHandles()
at System.Data.OleDb.OleDbDataReader.ReadRowset()
at System.Data.OleDb.OleDbDataReader.Read()
at System.Data.OleDb.OleDbDataReader.HasRowsRead()
at
System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior
behavior, String method)
at
System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior
behavior)
at
System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior
behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet
dataset, DataTable[] datatables, Int32 startRecord, Int32
maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[]
dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand
command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable
dataTable)
at
Test_Sybase.DataSet1TableAdapters.memberTableAdapter.Fill(memberDataTable
dataTable) in
C:\VS_projects\Test_Sybase\Test_Sybase\DataSet1.Designer.cs:line
3838
at Test_Sybase.Form1.Form1_Load(Object sender, EventArgs
e) in C:\VS_projects\Test_Sybase\Test_Sybase\Form1.cs:line
24
at System.Windows.Forms.Form.OnLoad(EventArgs e)

[Paul Vero [Sybase]]

Hi Jim,

Not sure why this occurs - what version of Provider are you using? I don't
think this
should be a problem to run.

We have samples for the native ADO.NET provider in the SDK 15.0
distribution - is is possible
to try one of those, modified for use with an OLE BD Provider to see if the
DataAdapter.Fill method causes such a problem?

Are you able to do this on some other table? Maybe it's data dependent, so
maybe table with single column as int or varchar might work, and
maybe something in that table causes the crash. Also if you could use the
RIBO utility - this will capture
the TDS between client and server - its a java based utility, found in
%SYBASE%\jutils-2_0\ribo - we should see if
at least data is coming from the ASE.

-Paul

<Jim Thomas> wrote in message news:4a79ec63.74a...@sybase.com...