Hi John,
Thanks for your response. Since I posted my query, I did manage to
connect to my remote database using integrated security instead of the
"sa" account. I added my user account to a SQL server group that I
created and then gave that group login rights to the database. That
works fine from my development machine but not if I package up Access
with the Access runtime and try to run on another machine that doesn't
have Access 2003 installed. So, I've solved one problem but now have
another. I've posted again to the Access group to see if anyone can
help me there.
Barb
John Bell wrote:[color=blue]
> Hi
>
> You may want to try connecting from your client using osql. It is not[/color]
clear[color=blue]
> if the manager software is on your client. If not then there seems to[/color]
be a[color=blue]
> network problem. Did you install it with the DISABLENETWORKPROTOCOLS
> option?
>[/color]
http://support.microsoft.com/default...21120121120120
[color=blue]
> to enable them see
>
http://support.microsoft.com/default...b;en-us;827204
>
> John
>
>
>
> "Barb" <funkybarb@gmail.com> wrote in message
> news:2ea50a4d.0504131151.43b8dbda@posting.google.c om...[color=green]
> > Hi there,
> >
> > I sincerely hope that someone out there can help. I have two
> > instances of the SQL 2000 Desktop Engine running. One is on my[/color][/color]
local[color=blue][color=green]
> > machine for development and the other is on another machine on our
> > network which is the production environment. I have built an[/color][/color]
Access[color=blue][color=green]
> > 2003 front end application which connects to this database. This
> > works fine locally, as you would expect. I successfully installed[/color][/color]
the[color=blue][color=green]
> > database on the production machine and am able to connect to it via
> > Access 2003 (using the Data Link Properties window) and from third
> > party database manager software (similar to Enterprise Manager). I[/color][/color]
am[color=blue][color=green]
> > not able to to connect to the database via my application.
> >
> > I am using the "sa" account with a strong password. This is my
> > connection string:
> >
> > strConnection = "Provider=sqloledb;DataSource=server02;User
> > Id=sa;Password=strong;Initial Catalog=Test"
> >
> > The error I'm getting is:
> >
> > "Connection cannot be used to perform this operation. It is either
> > closed or invalid in this context."
> >
> > The connection string is the only thing that changes in my code[/color][/color]
when I[color=blue][color=green]
> > switch from my local to my production database. Is there some[/color][/color]
reason[color=blue][color=green]
> > that I can't use the "sa" account in this fashion that I'm not[/color][/color]
aware[color=blue][color=green]
> > of? I'd rather not use integrated security for simplicity's sake[/color][/color]
as[color=blue][color=green]
> > this is a small, internal application. Also, I would have thought
> > that if that was the issue, I couldn't use "sa" at all, even[/color][/color]
locally.[color=blue][color=green]
> >
> > I'm going to post to the Access group as well but thought someone[/color][/color]
here[color=blue][color=green]
> > might have some advice to offer as well.
> >
> > Thanks,
> >
> > Barb[/color][/color]
