FreeTDS Development Group

[Andre Costa <brblueser AT uol.com.br>]

Hi all,

I am happy to say that this issue can be closed. At the end of the day, it
was indeed a DB permission problem -- Ops guys changed not only the
permission of the DB user I had set, but also the default database on the
MS-SQL Server I was trying to access. All the setup has been reviewed, and
I am (again) happily accessing our MS-SQL Server from my Linux box =)

(Isn't it great when Engineering and Operations go separate ways? *grin*
=T )

I would like to thank you all who replied to my posts, and apologize for
bothering with a non-FreeTDS issue. If it makes you feel better, rest
assured that your guidance was invaluable -- without it I could have never
narrowed down to the cause of the problem.

Best,

Andre

On Mon, 22 Apr 2002 23:36:56 -0200
Andre Costa <brblueser AT uol.com.br> wrote:

> Hi Brian,
> 
> yeah, I guess you're right and it's only symptomatic -- I experienced
> the same behavior (segfault) with SQSH, using the same connection
> parameters.
> 
> ... but, I am using 0.53... you mean it is fixed on the CVS snapshots?
> 
> Best,
> 
> Andre
> 
> On Mon, 22 Apr 2002 20:20:03 -0400 (EDT)
> Brian Bruns <camber AT ais.org> wrote:
> 
> > Andre,
> > 
> > From the stack trace you sent I believe the seg fault was fixed since 
> > 0.53, but the seg fault isn't the cause of the problem only
> > symptomatic.
> 
> ---
> You are currently subscribed to freetds as: [brblueser AT uol.com.br]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>