Re: Can't query linked Access database specified by UNC

From: Hans Nelsen (hnelsen_at_owh.com)
Date: 01/24/05 

Date: 24 Jan 2005 10:57:41 -0800

one thing that worked for me on loading dumps from UNCs is that i had
to use an absolute UNC path and not the share name.

for example:

if i had a share named "share" on folder X on my C drive

rather than going to //myComputer/share
i had to go to //myComputer/C$/X

and everything worked fine...it is worth a shot.

hth,
hans
Sue Hoegemeier wrote:
> Vadim,
> That last example wasn't a good one. Nonetheless, SQL Server
> doesn't start Access and then open a database.
> Other than security issues, combinations of MDAC/Jet drivers
> can also cause problems and you may want to check those. If
> you feel certain that this is a bug in SQL Server, you can
> open a case with product support. You will not be charged
> for the incident if it is a bug.
>
> -Sue
>
> On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
> <vr@myrealbox.nospam.com> wrote:
>
> >Hello Sue:
> >You wrote in conference
>
>microsoft.public.sqlserver.security,microsoft.public.sqlserver.server
on
> >Tue, 18 Jan 2005 16:11:38 -0700:
> >
> > SH> Yes...but you still need to check the permissions - the
> > SH> whole ldb thing. And you need to make sure the permissions
> > SH> are explicitly set. Logging on and starting access and
> > SH> opening the database manually is not the same thing.
> >
> >hmm... if I open the database manually, obviously, Access is
creating the
> >ldb... thus, it can do it... How is it not the same thing?
> >
> >And it looks like in sql server 2005 it works just fine.
> >
> >Vadim