Board index » delphi » Gerenal SQL error 13059 (SQL Server v 7)

Gerenal SQL error 13059 (SQL Server v 7)

Hello,

(This may be a repeat as I think my last one crashed, so I'm
resubmitting it)

I have a client who cannot run my application written in Delphi 3.0
running BDE 5.11.  The error we get is general sql 13059,  but nothing
more.  I get the same error with BDE as with my applciation.  I do
know that the client has Borland C++ and JBuilder 3 on the machine.  I
can connect with ISQL_w or Query Analyzer as it is known in version
7.0 of SQL Server.

TIA

Steve

 

Re:Gerenal SQL error 13059 (SQL Server v 7)


I saw this only when running sql tracer - it somehow eats the error message,
but in all other cases with general sql error comes the server's error
message, like
General SQL error [Microsoft][ODBC SQL Server Driver][SQL Server] <detailed
description of error>.

If you trap exception, be sure to check all errors:
except
 on E:EDBEngineError do
// either display E.Message
ShowMessage(E.Message);
// or go with a loop from 0 to error count-1
 for A := 0 to E.ErrorCount-1 do with E.Errors[A] do <something>

In this case if you check only Errors[0], you get "general SQL error" only.

--
----------------------
Regards
Robert Cerny
Remove both qwe when replying
email: robert.qwe.ce...@neosys.xrs.qwe.si

No questions via email, unless explicitly invited.

Quote
Stephen Eyton-Jones wrote in message

<3909b7d8.1426549...@forums.inprise.com>...
Quote
>Hello,

>(This may be a repeat as I think my last one crashed, so I'm
>resubmitting it)

>I have a client who cannot run my application written in Delphi 3.0
>running BDE 5.11.  The error we get is general sql 13059,  but nothing
>more.  I get the same error with BDE as with my applciation.  I do
>know that the client has Borland C++ and JBuilder 3 on the machine.  I
>can connect with ISQL_w or Query Analyzer as it is known in version
>7.0 of SQL Server.

>TIA

>Steve

Re:Gerenal SQL error 13059 (SQL Server v 7)


Steve,

I had the same problem.  I was putting in the full DOS path name of the
database, i.e. c:\im32\immain.???, in the BDE alias.  All that was
needed was the database name itself, i.e. immain.  Some SQL databases
(Interbase, Adaptive Server Anywhere) need the full path name.  Others
such as SQL Server 7, and I think DB2 only need the database name.

Al Willis

In article <3909b7d8.1426549...@forums.inprise.com>,
  sjo...@hmssoftware.ca (Stephen Eyton-Jones) wrote:

Quote
> Hello,

> (This may be a repeat as I think my last one crashed, so I'm
> resubmitting it)

> I have a client who cannot run my application written in Delphi 3.0
> running BDE 5.11.  The error we get is general sql 13059,  but nothing
> more.  I get the same error with BDE as with my applciation.  I do
> know that the client has Borland C++ and JBuilder 3 on the machine.  I
> can connect with ISQL_w or Query Analyzer as it is known in version
> 7.0 of SQL Server.

> TIA

> Steve

Sent via Deja.com http://www.deja.com/
Before you buy.

Re:Gerenal SQL error 13059 (SQL Server v 7)


Thanks Robert, but this is the context of the full error.  We have a
general error routine which merely dumps the exact error message when
it is unhandled.  

I forgot to mention however that I can reproduce the same error using
BDEADMIN, so it realy is not a programming issue, more a connectivity
issue.

On Fri, 28 Apr 2000 21:33:42 +0200, "Robert Cerny"

Quote
<robert.qwe.ce...@neosys.xrs.qwe.si> wrote:
>I saw this only when running sql tracer - it somehow eats the error message,
>but in all other cases with general sql error comes the server's error
>message, like
>General SQL error [Microsoft][ODBC SQL Server Driver][SQL Server] <detailed
>description of error>.

>If you trap exception, be sure to check all errors:
>except
> on E:EDBEngineError do
>// either display E.Message
>ShowMessage(E.Message);
>// or go with a loop from 0 to error count-1
> for A := 0 to E.ErrorCount-1 do with E.Errors[A] do <something>

>In this case if you check only Errors[0], you get "general SQL error" only.

>--

Re:Gerenal SQL error 13059 (SQL Server v 7)


Stephen,

Check the Database Name field of the BDE alias.  It should NOT be a full DOS
path name such as c:\abc\xyz.mdf.  Only use the xyz in the field.

Al Willis

Quote
"Stephen Eyton-Jones" <sjo...@hmssoftware.ca> wrote in message

news:3909b7d8.1426549679@forums.inprise.com...
Quote
> Hello,

> (This may be a repeat as I think my last one crashed, so I'm
> resubmitting it)

> I have a client who cannot run my application written in Delphi 3.0
> running BDE 5.11.  The error we get is general sql 13059,  but nothing
> more.  I get the same error with BDE as with my applciation.  I do
> know that the client has Borland C++ and JBuilder 3 on the machine.  I
> can connect with ISQL_w or Query Analyzer as it is known in version
> 7.0 of SQL Server.

> TIA

> Steve

Re:Gerenal SQL error 13059 (SQL Server v 7)


Thanks, I've checked, it is the database name as we expect, and the
error if the name were wrong would indicate that it could not find the
database in the Sysdatabases table.

On Fri, 28 Apr 2000 22:47:26 -0500, "Al Willis" <alwil...@pdq.net>
wrote:

Quote
>Stephen,

>Check the Database Name field of the BDE alias.  It should NOT be a full DOS
>path name such as c:\abc\xyz.mdf.  Only use the xyz in the field.

>Al Willis

>"Stephen Eyton-Jones" <sjo...@hmssoftware.ca> wrote in message
>news:3909b7d8.1426549679@forums.inprise.com...
>> Hello,

>> (This may be a repeat as I think my last one crashed, so I'm
>> resubmitting it)

>> I have a client who cannot run my application written in Delphi 3.0
>> running BDE 5.11.  The error we get is general sql 13059,  but nothing
>> more.  I get the same error with BDE as with my applciation.  I do
>> know that the client has Borland C++ and JBuilder 3 on the machine.  I
>> can connect with ISQL_w or Query Analyzer as it is known in version
>> 7.0 of SQL Server.

>> TIA

>> Steve

Other Threads