Only 1 user at a time can open the access program with Windows 7 p

  • Thread starter Thread starter Bill
  • Start date Start date
B

Bill

Hello, I have created a MSaccess database in Office 2000 format over a year
ago. This is a multi-user enviroment and multiple users can access at the
same time (using XP platform). Now that I have begun to buy new computers
(w/Windows 7 platform) I have found that only one user at a time (Windows 7
computers) can access the database. Xp computers still access fine in
mult-user enviroment... I have set trusts and macros ......Any ideas....Thanks
 
Bill

You didn't mention, so I'll ask...

Is the application "split" - front-end (copy) on each user's PC, (single)
back-end on your LAN?

Any chance the new PCs are not being permitted to the back-end
folders/files?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
Jeff,
I have it split on the server (Front-End - Main Program..Reports...
forms....) (Back-End - modules folder with dbs linked to Main).... Works
fine on XP machines... Do you think Moving the front-end to each computer
would have a bigger impact?....Thanks
 
I disabled UAC on the users PC's and my front ends started working just
fine. I don't know if this fits in with your companies security policies.
 
If you have a single "front-end", sitting on your server, then every user
essentially downloads the application front-end to use it. I'm surprised:
1) you don't have serious on-going corruption problems
2) the network police haven't shut you down for over-using the network.

Yes, the preferred design is a copy of the front-end on each PC, linked to
the tables in a "back-end". That back-end data store can be another Access
file, or a SQL-Server database, or ...

.... ?and the permissions?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
If you have a single "front-end", sitting on your server, then every user
essentially downloads the application front-end to use it.  I'm surprised:
  1) you don't have serious on-going corruption problems
  2) the network police haven't shut you down for over-using the network.

Yes, the preferred design is a copy of the front-end on each PC, linked to
the tables in a "back-end".  That back-end data store can be another Access
file, or a SQL-Server database, or ...

... ?and the permissions?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.







- Show quoted text -
Click to expand...

Google "AutoFE". It's Tony T's absolutely beautiful routine to
distribute front end Access databases.
 
Jeff,

I have not had a problem with file corruption... However I think the network
slowdown is in relation to this front-end as you discussed. I have moved the
front-end to each workstation...it works great..and fast...everyone can get
in and no problems getting to the back-end regardless of Windows version... I
appreciate your help it was very useful....

Bill
 
John,

I disabled the UAC and the users were able to get in...However the operation
of the program is slower than before. What I ended up doing was moving the
front-end to the users computer (from the server) and re-enabled the UAC. The
programs worked great...fast...

Thank You for your input....

Bill
 
Hi Bill,

I see you've received satisfactory answers and are on your way to happy
users. I have a question for you now though, if you don't mind.

A while back I asked if anyone was using A2k with Windows 7 yet and got a
response from Tony Toews that I haven't had time to implement. But now YOU
have experience with this. So, just wondering....

Is that Windows 7 user, who's now working great, an administrator account,
or a user account? And if admin account, can it work if you switch to a
limited user account on that same machine?

I'm happy to see that a Windows 7 machine doesn't seem to have any problems
with A2K running over a network, because the Windows 7 compatibility list
says a Office2k user needs to "upgrade to current version" or some such.

Thanks for any response,
me
 
Me,

My Workstations consisit of Xp, Vista, Windows 7...My network is Windows
Server 2003. I am running a A2k Formated program, however, the program is
running through MS Office 2007. So in essence I have upgraded my MS Office,
(but did not update for the windows 7 workstations basis) however the format
is still A2k. I ran prior on MS Office 2003.

The Windows 7 accounts are both administrator & User accounts which are
both functioning properly now for multi-user mode. I currently do not have
limited user accounts on the system. I will change an account and test the
system... currently not sure how it will act in limited-user.

Bill
 
Thanks for the response, Bill.

If you like to play around and see what happens, go ahead and change one of
those Win 7 accounts and see what happens and post back--still probably of
interest here. But it won't test what I need to test. All my users are
running either WinXP or Vista with the runtime A2k. Everything works fine.
But with Microsoft's warning that users need to "upgrade to current
versions" for proper operation of access files, I'm concerned that runtime
A2k under Win 7 isn't going to cut it. And since you won't be testing that
since your users run '07 the info won't help me.

Guess I'm stuck having to upgrade one of my systems here and see what
happens. If it doesn't work, I'll try what Tony suggested.

Thanks anyway!
me
 
Back
Top