Hi Simon,
Thanks for the suggestion but I don't think that's the problem. I can
connect to the database from the other machine with my account and
another user account that are in the global and local SQL Server group
(using Windows Authentication via a third party bit of software similar
to Enterprise Manager). I have SP3 installed on the remote machine so
the SP3a issue wouldn't have come into play.
My last guess is that it must be something to do with the package
itself.
Thanks again ... at least I know that it's not security related.
B.
Simon Hayes wrote:[color=blue]
> "Barb" <funkybarb@gmail.com> wrote in message
> news:2ea50a4d.0504181325.4531f344@posting.google.c om...[color=green]
> > Hi there,
> >
> > I have an Access front end application that uses a SQL Server 2000
> > Desktop Edition backend. I have created a package with the Access
> > 2003 runtime that I'd now like to deploy. I have created a global
> > group in the domain and placed the users that I'd like to give[/color][/color]
access[color=blue][color=green]
> > to the database (via my application front end) in that group. I've
> > then created a local group on the SQL Server machine and added my
> > global SQL Server group to it. I've also added that local group as
> > database user from SQL Server. From my reading of the various
> > material on the Internet this should work but it doesn't. I can't
> > access the database via the application from any machine other than[/color][/color]
my[color=blue][color=green]
> > development machine. My VBA code specifies integrated security for
> > the connection string.
> >
> > Help please! I'm so close to deploying this and now I'm bogged[/color][/color]
down[color=blue][color=green]
> > in security. Any ideas anyone has would be appreciated. Account
> > administration and Windows security is not my strong suit.
> >
> > Barb[/color]
>
> The first thing to check would be network access to MSDE - you don't[/color]
mention[color=blue]
> which version you've installed, but starting from SP3a, network[/color]
access is[color=blue]
> disabled by default, so it's normal that users can't connect from[/color]
another[color=blue]
> machine. You can use the Server Network Utility to change this, and[/color]
these[color=blue]
> articles give more information:
>
>
http://support.microsoft.com/default...b;en-us;814130
>
http://support.microsoft.com/default...b;en-us;319930
>
> Simon[/color]
