Re: different environment fails to fill a dataset
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Sat, 8 Apr 2006 08:57:47 -0400
What exactly is different about that form from the rest? Have you tried
running profiler to see what is actually happening on the sql server side?
--
Andrew J. Kelly SQL MVP
"rseedle" <rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:51D13828-57D3-4375-9F6B-AA23BC9C738C@xxxxxxxxxxxxxxxx
Andrew:
Well I recreated the login but it didn't make any difference. The form
that
didn't work before still doesn't work and the forms that did work before
still work. Any other suggestions ?
Randy
"Andrew J. Kelly" wrote:
You might have lost the relationship of the Login to the user in the db.
It
may be able to connect but not get to the db itself. Try dropping the
login
and readding it making sure to specify the database access when you do.
--
Andrew J. Kelly SQL MVP
"rseedle" <rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:58084FB0-43E4-480D-B328-E2633EEF4CCE@xxxxxxxxxxxxxxxx
I am using "Integrated Security=SSPI;" (Windows login info) in all of
the
connection strings used in the various forms. Will it still be
necessary
to
do something with sp_change_users_login ?
Randy
"Andrew J. Kelly" wrote:
Did you resync the logins to the users in that db after you attached
it?
If
not check out sp_change_users_login in BooksOnLine.
--
Andrew J. Kelly SQL MVP
"rseedle" <rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C298B6AF-C57D-40EE-905C-CB50F29126F3@xxxxxxxxxxxxxxxx
I have a C# client application that uses SQL Server as a backend. It
works
fine on my development workstation. But when I moved it to another
test
workstation four out of the five winforms worked fine but one
doesn't.
The
one that doesn't can open the connection and return the server
version
as
a
test of whether the open worked right. I does. But when you run the
oledbadapter.fill command to fill the dataset it fails. It acts as
if
it
can't open the server. Further reading shows that the fill command
can
actually open a connection on its own if necessary without the open
command.
Is there anything in the environment or SQL Server that could be
causing
this
rejection. The SQL Server database was detached, copied, and then
reattached
on the test workstation. SO it should be a duplicate.
Randy
.
- Follow-Ups:
- Re: different environment fails to fill a dataset
- From: rseedle
- Re: different environment fails to fill a dataset
- References:
- Re: different environment fails to fill a dataset
- From: Andrew J. Kelly
- Re: different environment fails to fill a dataset
- From: Andrew J. Kelly
- Re: different environment fails to fill a dataset
- From: rseedle
- Re: different environment fails to fill a dataset
- Prev by Date: Re: different environment fails to fill a dataset
- Next by Date: Re: different environment fails to fill a dataset
- Previous by thread: Re: different environment fails to fill a dataset
- Next by thread: Re: different environment fails to fill a dataset
- Index(es):
Relevant Pages
|