Limit Number of Users

[Guest]

Hello,

Is there a way to limit the number of users logged in at one time. I would
like to limit the number of users to five and have a message box send a
message indicating the limit has been reached and to log in later.

Thanks

 

[Jeff Boyce]

Why?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

This database is hit with users all at once on a quarterly basis. The user
inputs their Safety inspection(approx 102 yes/no answers) and a Word document
is generated based on the input by the user(s). I have tested the generation
of the Word document on different computers throughout the facility the times
between the execute print command and the actual print time varies among
different computers.

If the number of users are limited on the front end then the management of
the entire process will be smoother.

 

[Guest]

The database has 102 (Yes/No responses) and 10 memo fields with regard to
safety inspections for a facility. The data entry is not a problem. A Word
document is generated based on a query from the user. The responses (yes/no)
are counted and summed and a report (in Word ) is generated based on the
users input.

Each computer within the facility generates the Word document at its own
pace, therefore, limiting the number of users to five would facilitate
smoother flow of the process. The users hit this database once a quarter (on
the day it is due most of the time) and expect things to run smoothly.

Thanks,

 

[Jeff Boyce]

I guess I'm not understanding.

If the data entry portion is not an issue, and if the Word document is
generated on the user's (local) PC, how is the system being slowed down?

Oooh! Does each PC have its own copy of a "front-end", or do you have
everyone "sharing" a single front-end, located on a server? Or even
everyone using a single .mdb file (not separated into front-end & back-end)?

(I'll suggest creating a back-end on a server and a copy of a front-end on
each PC, if you haven't done so already.)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

Jeff,

Thanks for your reply. "everyone "sharing" a single front-end, located on a
server" is the situation here. At times the users vary each time the data is
filled in and I would have to give each new user the front-end and take away
the front end off each computer in which the user is not supposed to fill in
the data. Would you solution still apply?

I appreciate your input.

 

[Jeff Boyce]

I'm not clear why you'd have to take away the front-end. Could you tell the
users not to use the application when they don't need to?

The recommended design is a copy of a front-end on EACH user PC, not sharing
a single front-end located on a network/server.

I think I understand now why your application was bogging down ... everyone
hitting a single front-end at once and trying to get it to work across a LAN
(this is a LAN, not a WAN, right?!) would seriously stress it.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

Jeff,

Yes, this is going across a LAN. I've plenty to do.

Many Thanks,

 

[Ron2006]

What we have done in some situations is

1) BE on the server

2) FE on the server

3) BAT file on the server that copies the FE to the local computer,
executes it, and then deletes the FE from the local computer when done.

4) A Short cut is placed on each computer that needs it that executes
the BAT file NOT the single version of the FE.

Advantage:
Proper FE/BE setup
User ALWAYS has the most recent version.

Ron

 

[Guest]

Ron,

Can you point me in the right direction on your #3? I can't say I have ever
done something like before. Maybe, a reference online.

Thanks,

 

[Ron2006]

1) Here was our sample bat file-

TimeEntry.bat
_____________________________________________________________
@echo off
copy "V:\TEAM FOLDERS\Dan's Team\Database\OS Time Card Entry.mdb"
C:\OStimecard.MDB /Y

C:\OStimecard.MDB

del C:\OStimecard.MDB

exit
_____________________________________________________________

Note: the copy and the line immediately below it is actually 1 line in
the file.
Note: The delete is not absolutely necessary because the file is
overlayed each time.

2) Create a shortcut to the bat file and rename it for clarity
purposes. I renamed ours to: "Run Time Entry Application"

3) Anybody that needs the application should then copy that shortcut
down onto their desktop.

Ron

 

[Ron2006]

Here is a DOS Bat File Primer reference:


http://www.exclamationsoft.com/exclamationsoft/netmailbot/help/website/HowToCreateADOSBatchFile.html

 

[Guest]

Ron,

Many thanks - I'll give this a try.