RE: big problem!!!!!
- From: "Cowboy (Gregory A. Beamer) - MVP" <NoSpamMgbworld@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 May 2005 09:54:33 -0700
IDEA: Dbf=C:\SqlAny\Demo.db
Not sure about Sybase (have not used it), but the location of the database
is most likely your issue. This gives you a couple of options:
1) Break down ASP.NET (and possibly IIS) security to allow access to this
file path location. Potential security hole?
2) Move the database to a directory your app has access to. Potential
security hole?
3) Set up an interface (non ASP.NET) to wrap the database access. If you
want to make it easy to move from machine to machine, consider a web service
(Remoting style, not ASMX) and have it serve from the database. DataSets are
highly conducive to web service serving of data (ie, SOAP).
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Wilco" wrote:
> hello,
>
> we use this ODBC connectionstring:
> "Driver=Sybase SQL Anywhere 5.0;Dbf=C:\SqlAny\Demo.db;Uid=me;Pwd=me"
>
> in a windows application it works fine, but in an asp.net applicatie we get
> the next error:
>
> ERROR [08001] [Sybase][ODBC Driver]Unable to connect to database server:
> unable to start database engine ERROR [01000] [Microsoft][ODBC Driver
> Manager] The driver doesn't support the version of ODBC behavior that the
> application requested (see SQLSetEnvAttr).
>
> any ideas?
>
>
>
>
>
.
- Follow-Ups:
- RE: big problem!!!!!
- From: Wilco
- RE: big problem!!!!!
- References:
- big problem!!!!!
- From: Wilco
- big problem!!!!!
- Prev by Date: RE: New row in a DataList
- Next by Date: Transactions & SQL Stored Procedures
- Previous by thread: big problem!!!!!
- Next by thread: RE: big problem!!!!!
- Index(es):
Relevant Pages
|