Weird sharing problem Win XP Pro - Win XP Home

Hi all,



I ran to a very strange problem last week:

One of my clients is running an acc2k app for years.

So now he wants to share the backend with another workstation in order to
work simultaneously.

Should be no problem...heh ??



So, we installed this other PC, added this pc to the local workgroup,
enabled file- and printer sharing and such.

We shared the directory with the be, added a network connection and tried to
attach to the be-tables.

"No permission or database in use" is the error... but... the db is NOT in
use...!!



Weird... all the other files in the directory can be edited, renamed,
deleted but the specific be-mdb we need is not accessible...

Did the 'usual' stuff (checked settings, rebooted and such), but no joy.

The PC that we want to act as the 'db-server' (sharing the folder where the
be resides) has Win XP Home...

(this is the PC that is running the app for years now)

The PC trying to connect has Win XP Pro...

Both PC's have Access2000 installed.

The app runs fine on the Win XP Pro PC with the be installed locally... but
I simply can't access the be- mdb.



So PC2 (XP Pro) can not access the be on PC1 (XP Home)

This is some weird permissions-problem I guess but I am unable to solve
this...

I hope the problem is clear... any ideas ???



FYI: I tried to do the same thing the other way around yesterday and that
works! Go figure...!!

I am sure we are talking about the *very same* files, because I did copy the
files back and forth ...

I mean with the other way around that PC1 (XP Home) can access and connect
to the be on PC2 (XP Pro).

But that is not what the client wants...

I know we should not use XP Home but ....


Thanks
Arno R


.

Relevant Pages

  • Re: Previous User Settings
    ... I have upgraded these to XP Pro, leaving the previous settings inplace. ... The problem that i am having is that prior to installing XP Pro the two clients had some bespoke software that was available to any user who logged on to client. ... > Now when User A logs on to the client the bespoke app is available, however when User B or C loggs on then the application is not available. ...
    (microsoft.public.windows.server.sbs)
  • Re: MSAccess to Web App
    ... I agree that an A97 app is long in the tooth nowadays, ... PC- based application, that is, support of as many different PC ... This is something that *you* care about but your clients don't. ... Sure, they know they are paying for only a year, but they don't like ...
    (comp.databases.ms-access)
  • Re: MDE and runtime
    ... but at this point I may be sending the app to clients with nothing more ... I have Access 2003 with VB Tools, so I have no way to compile to an earlier ... reference sits in the ...Office10 folder. ...
    (microsoft.public.access.devtoolkits)
  • Re: RemoteApp Dialogs Disappear
    ... I tested it with WordPad and it happens there as well. ... only with message boxes that generate a beep. ... We are publishing our app through RemoteApp (Terminal Services ... this behavior varies between clients. ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows XP and VFP 8.0
    ... This error message is not a VFP error. ... Have you contacted the developer to ask him what might prompt this error? ... >The app is served in a shared folver by a Win98 pc. ... Clients are WinXP, ...
    (microsoft.public.fox.helpwanted)