Connect to back end for non logged on user

[Mike MacSween]

FE on workstations/BE on server. W2K to W2K server.

One of these users logs on to her local machine, not the domain (although
the machine is networked and she has permissions). I'm not there now, but my
experience here is that if you try to start on Access app logged onto the
local machine I get empty forms. Until I actually use network neighbourhood
to connect to some file or other on the server, via a logon dialogue.

Anybody know of a way to connect a user to the server/BE on the server
without logging them onto the domain?

Yours, Mike MacSween

[Tom van Stiphout]

On Mon, 15 Dec 2003 09:15:57 -0000, "Mike MacSween"
<mi************ ******@btintern et.com> wrote:

What do you have in mind? A procedure to use network resources
without being validated by the server? And then presumably go where
you want to, defeating the entire Windows security infrastructure? No
way, Jose!

-Tom.

FE on workstations/BE on server. W2K to W2K server.

One of these users logs on to her local machine, not the domain (although
the machine is networked and she has permissions). I'm not there now, but my
experience here is that if you try to start on Access app logged onto the
local machine I get empty forms. Until I actually use network neighbourhood
to connect to some file or other on the server, via a logon dialogue.

Anybody know of a way to connect a user to the server/BE on the server
without logging them onto the domain?

Yours, Mike MacSween

[Mike MacSween]

"Tom van Stiphout" <to*****@no.spa m.cox.net> wrote in message
news:eh******** *************** *********@4ax.c om...

On Mon, 15 Dec 2003 09:15:57 -0000, "Mike MacSween"
<mi************ ******@btintern et.com> wrote:

What do you have in mind? A procedure to use network resources
without being validated by the server? And then presumably go where
you want to, defeating the entire Windows security infrastructure? No
way, Jose!

Mmm. Perhaps I didn't explain that very well.

Take this scenario. The user boots the workstation and chooses the 'logon to
xxxxx (this machine)'. In other words they aren't logging on to the network
domain. But the BE of the database lives on the server. So when they open
the FE - no records! Here I find that if I navigate to the server from
Explorer first, which will involve a 'enter the user name and password of a
user with rights to blah blah' I can open the FE, with records.

Does that make sense? Maybe not.

The reason? This user appears to 'have to' log on to the local machine
because of some licensing restriction with their accounting software. I
think they'd have to buy another licence if she logged onto the network. But
today she was fairly adamant she _didn't_ want access to the database, so
problem solved.

I agree. I'd rather work within the Windows security infrastructure, the way
it's meant to be.

Cheers, Mike