Upgraded to Vista. Finally I think I have the network issues resolved (4
computers, using NetworkMagic).

However, since day one, two computers are unable to access Access unless
they are the sole user of Access.

3 computers have Vista (2 Home Basic, 1 Home Premium), 1 WinXP.
4 computers have Access 2007.
4 computers have Quick Books multi-user.

Access' back-end resides on Home Basic. Also has front-end.
The other 3 computers have front-end pointing to the back-end.

Here's what I know:

1. computer with front and back-end works fine for Access.

2. XP computer works fine for Access.

3. Other two do not work unless they are the only computer accessing the
back-end and then it takes FOREVER.

4. All 4 computers share QB files resident on the computer with Access
back-end. All 4 QBs work fine.

5. I am able to see all computers on the network and have no sharing issues
(that are evident--I can get to everything Access, everywhere.)

6. The Vista forum does not respond to this question.

Ideas? Has anyone run into this with Access 2007? Any other program.

This is very frustrating -- and severely limiting.

--
Skunk

The symptoms you describe in terms of only allowing one user into the data
base means that user does not have full rights to that directory.

Users need 100% full rights that directory. this include file creation, and
file deletion rights.

What happens when MS access starts up is it creates a temporary record
locking file that allows it to work in multi user mode, if access does not
have sufficient permissions to that directory, then it cannot create this
file and thus it defaults into single user mode. This is why some computers
allow multiuser mode when used first to go in, and some other computers do
not, someone is lacking correct permissions to that directory.


As for your long delay in performance issues, I suggest that you keep a
persistent connection of the front end to the back end.
The list of issues in terms of slow startup and long delays etc. can be
solved by working your way through the following list of performance things
to check
http://www.granite.ab.ca/access/performancefaq.htm


And by the way you are installing the database front end of each computer?
correct? this can also be a source of problems because of permissions and
locking rights placed on the front end, so you really do not what allow
multiple users into the same front end.

I explain the concept of splitting and installing the database on each
computer in the following article of mine:
http://www.members.shaw.ca/AlbertKal...plit/index.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

Thanks for responding, Albert.

I have used individual front-ends for each computer always.

It makes sense that my problem is one of permissions, but, I think I have
moved past that issue probability. I was unable to even see the computer
with the back-end after reinstalling Vista on two machines. (New computer
bad network on mother board, and disk error support suggested Vista reinstall
on the other)

I found many references to Network Magic (part of Cisco) in the Vista groups
and am in the trial of that...so far, I am crazy about it. Sure does simplify
things. I can see my shared folder and access the files (including the
back-end).

Note that when, from a computer other than the back-end, I select the
back-end to my db, it hangs if anyone else is using it. I can see it,
double-click to launch -- but it hangs if in use. This says to me
permissions etc are OK in Vista, right?

Its Access 2007 and I am wondering if there is some hidden or not obvious
Access switch to allow/disallow multi-use if in Vista. The XP computer can
retrieve and update fine. But not the two Vistas. I have reinstalled them
also. And, yes, they are all legal, registered versions and all are up to
date with MS updates.

What do you think?



--
Skunk


"Albert D. Kallal" wrote:

> The symptoms you describe in terms of only allowing one user into the data
> base means that user does not have full rights to that directory.
>
> Users need 100% full rights that directory. this include file creation, and
> file deletion rights.
>
> What happens when MS access starts up is it creates a temporary record
> locking file that allows it to work in multi user mode, if access does not
> have sufficient permissions to that directory, then it cannot create this
> file and thus it defaults into single user mode. This is why some computers
> allow multiuser mode when used first to go in, and some other computers do
> not, someone is lacking correct permissions to that directory.
>
>
> As for your long delay in performance issues, I suggest that you keep a
> persistent connection of the front end to the back end.
> The list of issues in terms of slow startup and long delays etc. can be
> solved by working your way through the following list of performance things
> to check
> http://www.granite.ab.ca/access/performancefaq.htm
>
>
> And by the way you are installing the database front end of each computer?
> correct? this can also be a source of problems because of permissions and
> locking rights placed on the front end, so you really do not what allow
> multiple users into the same front end.
>
> I explain the concept of splitting and installing the database on each
> computer in the following article of mine:
> http://www.members.shaw.ca/AlbertKal...plit/index.htm
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal@msn.com
>
>
>

"Skunk" <webmaster@petsatlanta.com> wrote in message
news:51112DF9-2DE9-43F4-A334-DB776AE8DF32@microsoft.com...
> Thanks for responding, Albert.
>

>I was unable to even see the computer
> with the back-end after reinstalling Vista on two machines. (New computer
> bad network on mother board, and disk error support suggested Vista
> reinstall
> on the other)


Well, then after doing the above, I assume you could see and use the
files?????

>
> I found many references to Network Magic

I have no idea what Network magic is? Not sure why it relevant here at
all???

At the end of the day, you simply need to ensure that users have full rights
to the directory. Vista is more aggressive in terms of security. In fact,
for testing, I would turn off all firewalls on both ends during testing
until you get things working. Also, stay 100% away from using the c:\program
files\ directory..as that really now only read only and you can NOT play
around in there anymore.

>
> Note that when, from a computer other than the back-end, I select the
> back-end to my db, it hangs if anyone else is using it. I can see it,
> double-click to launch -- but it hangs if in use. This says to me
> permissions etc are OK in Vista, right?

Actually, it hints that something is wrong. Also, there is bit of gray here
when you talk about "select the back end". You might want to expand on that.
I would pre-link the back end before distribion to each machine.

Another thing to check is after the one user has the applicaton open and
running, do you see the record locking file created in the back end dir?
Take a look at the permissiosn on that locking file.

>
> Its Access 2007 and I am wondering if there is some hidden or not obvious
> Access switch to allow/disallow multi-use if in Vista.

Absolutely nothing has changed, it is simple file that you open sitting on a
folder, nothing more, nothing less...


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

Turns out my network setup, file sharing, front-end and back-end are all
working fine.

When revisiting MS Knowledge Base and searching - again, I came accross a
recent Hotfix for this issue. Solved my problem.

FYI -- KB article 935366

Link: http://support.microsoft.com/kb/935366

--
Skunk


"Albert D. Kallal" wrote:

> "Skunk" <webmaster@petsatlanta.com> wrote in message
> news:51112DF9-2DE9-43F4-A334-DB776AE8DF32@microsoft.com...
> > Thanks for responding, Albert.
> >
>
> >I was unable to even see the computer
> > with the back-end after reinstalling Vista on two machines. (New computer
> > bad network on mother board, and disk error support suggested Vista
> > reinstall
> > on the other)
>
>
> Well, then after doing the above, I assume you could see and use the
> files?????
>
> >
> > I found many references to Network Magic
>
> I have no idea what Network magic is? Not sure why it relevant here at
> all???
>
> At the end of the day, you simply need to ensure that users have full rights
> to the directory. Vista is more aggressive in terms of security. In fact,
> for testing, I would turn off all firewalls on both ends during testing
> until you get things working. Also, stay 100% away from using the c:\program
> files\ directory..as that really now only read only and you can NOT play
> around in there anymore.
>
> >
> > Note that when, from a computer other than the back-end, I select the
> > back-end to my db, it hangs if anyone else is using it. I can see it,
> > double-click to launch -- but it hangs if in use. This says to me
> > permissions etc are OK in Vista, right?
>
> Actually, it hints that something is wrong. Also, there is bit of gray here
> when you talk about "select the back end". You might want to expand on that.
> I would pre-link the back end before distribion to each machine.
>
> Another thing to check is after the one user has the applicaton open and
> running, do you see the record locking file created in the back end dir?
> Take a look at the permissiosn on that locking file.
>
> >
> > Its Access 2007 and I am wondering if there is some hidden or not obvious
> > Access switch to allow/disallow multi-use if in Vista.
>
> Absolutely nothing has changed, it is simple file that you open sitting on a
> folder, nothing more, nothing less...
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal@msn.com
>
>
>

Skunk <webmaster@petsatlanta.com> wrote:

>When revisiting MS Knowledge Base and searching - again, I came accross a
>recent Hotfix for this issue. Solved my problem.
>
>FYI -- KB article 935366
>Link: http://support.microsoft.com/kb/935366

Thanks very much for posting back. You've helped a bunch of other
people who will be having this same problem in the future.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Skunk <webmaster@petsatlanta.com> wrote:

>FYI -- KB article 935366
>Link: http://support.microsoft.com/kb/935366

Also blogged with credit to you.
http://msmvps.com/blogs/access/archi...-database.aspx

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/