MS Access on a LAN

[Thats Me]

Background: Access 2000 running on Windows 2000, Did not design
inherited (three previous database maintainers in last 18 months),
Non-existent comments for existing code modules and objects, six
users on LAN, BE on shared server. Each user has own FE to allow
special report & query creation, each user has common forms for input
and edit of main table data, Main data tables are linked from BE,
special tables are stored in users FE. Default open Mode is shared;
Default Record lock is edited record.

Problem: Only one user at a time can be in database record editing
fails and second users instance of Access locks up.

Help needed, ideas on where to look to solve this problem welcome.
Reply in newsgroup appreciated as only check the listed email account
once a week.

Have done five Access projects on LANs but they were only on two or
three computers and always one user at a time, i.e. data entry during
day, detail reports at night, manager summary reports only no data
entry.

We are getting two additional data entry people and I need to get
this fixed, I know a real SQL Server as BE would be the best
solution, but powers that be want to stay with Access.

Can't ID where I work but computers are new Dells with Windows 2000
and MSOffice 2000, no pre-compiled code can be loaded to HD's. To
load compiled code (such as a MDE or DLL) must provide to network
manager in uncompiled format, they review then create compiled
version and push to selected computers or send a tech with a CD in
hand to load, No admin or power user rights on any user machine.

Have a nice day. ld****@NOPANTS.juno.com

Remove NOPANTS. To reply by direct E-Mail;
Support: The Right to Privacy and Anti-SPAM projects

[Albert D. Kallal]

"Thats Me" <yq****@whab.pbz> wrote in message
news:41***************@news-server.ec.rr.com...

Background: Access 2000 running on Windows 2000, Did not design
inherited (three previous database maintainers in last 18 months),
Non-existent comments for existing code modules and objects, six
users on LAN, BE on shared server. Each user has own FE to allow
special report & query creation,
Hum, usually I distribute a mde, and users are NOT allowed to change the
application. In fact, I usually hide all of the ms-access application. It is
VERY
rare that a well designed application needs uses to modify reports and
queries, and in most cases this means the original designs and requirements
were not done well. (as you mention, this is not your fault..but end users
should NOT have to modify things to make a application work).
Main data tables are linked from BE,
special tables are stored in users FE. Default open Mode is shared;
Default Record lock is edited record.
The above sounds ok. Often, single user means that the users do not have
FULL PERMISSIONS to the back end folder share. I going to repeat this once,
and only once:

Users need full permissions to the back end folder!. That means read/write
and create and delete permissions.

If your users do not have full permissions to the back end folder, then
ms-access cannot create locking files on the BE that are required for
multi-user operation. When this happens, ms-access opens the files in single
user mode.

To
load compiled code (such as a MDE or DLL) must provide to network
manager in uncompiled format, they review then create compiled
version and push to selected computers

The above makes sense. However, it would be really insane if you are still
allowed to distribute a mdb FE to the users! You realize that a MDB lets
END USERS compile and write their own code! If you are telling me the
policy is that to distribute a mde, it must be reviewed before being
converted
into a mde, and distributed. However, you would sill be free to distribute
a mdb! In fact, if you distribute a mdb, each time it runs, it does compile
the code, but what is much worse, is that end users are able to create
and develop and changing code. So, in effect, you are telling
me that end users would be free to modify and write code, yet you the
developer is supposed to be writing code can't do the same!!

I suspect I am missing reading the above, or you did not word it correctly.

Anyway, distributing a mdb to the end users means they are free to develop
and compile code them selves, but if you are not allowed to distribute
a mde, then that company is in silly land! If you give all users a mde,
then they can't modify or change the code sent to them.

Anyway, I would first check the permissions on the shared folder(s) where
the BE resides. As mentioned, users need full permissions to the BE folder
(again, I said FULL permissions!).
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal

[Thats Me]

On Sat, 29 Jan 2005 22:31:11 GMT, "Albert D. Kallal"
<Pl*******************@msn.com> wrote:

---------<reply edited>------------------------

"Thats Me" <yq****@whab.pbz> wrote in message
news:41***************@news-server.ec.rr.com...

Background: Access 2000 running on Windows 2000, Did not design
inherited (three previous database maintainers in last 18 months),
Non-existent comments for existing code modules and objects, six
users on LAN, BE on shared server. Each user has own FE to allow
special report & query creation,
The above sounds ok. Often, single user means that the users do not have
FULL PERMISSIONS to the back end folder share. I going to repeat this once,
and only once:

Users need full permissions to the back end folder!. That means read/write
and create and delete permissions.

They are supose to have those permissions for the folder on the share
where the BE resides, Thanks for the hint I will check that out.
If your users do not have full permissions to the back end folder, then
ms-access cannot create locking files on the BE that are required for
multi-user operation. When this happens, ms-access opens the files in single
user mode.

To
load compiled code (such as a MDE or DLL) must provide to network
manager in uncompiled format, they review then create compiled
version and push to selected computers
The above makes sense. However, it would be really insane if you are still
allowed to distribute a mdb FE to the users! You realize that a MDB lets
END USERS compile and write their own code! If you are telling me the
policy is that to distribute a mde, it must be reviewed before being
converted
into a mde, and distributed. However, you would sill be free to distribute
a mdb! In fact, if you distribute a mdb, each time it runs, it does compile
the code, but what is much worse, is that end users are able to create
and develop and changing code. So, in effect, you are telling
me that end users would be free to modify and write code, yet you the
developer is supposed to be writing code can't do the same!!

I suspect I am missing reading the above, or you did not word it correctly.

I worded it as the policy is and yes I am aware of the security hole
and the limitations on my maintenance and the ease of users breaking
it with their "modifications".

I am on site contractor labor and part of my tasking is to maintain
this animal adding such features as the customer desires. I guess
that is part of why I'm the fourth maintainer in 18 months. Customer
developed the basic application and owns it.
Anyway, distributing a mdb to the end users means they are free to develop
and compile code them selves, but if you are not allowed to distribute
a mde, then that company is in silly land! If you give all users a mde,
then they can't modify or change the code sent to them. In silly land, that is putting it mildly. I was thinking more like
needing plexiglass hatch in abdomen to see where they were going.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal

Have a nice day. ld****@NOPANTS.juno.com

Remove NOPANTS. To reply by direct E-Mail;
Support: The Right to Privacy and Anti-SPAM projects

[Salad]

Thats Me wrote:

Background: Access 2000 running on Windows 2000, Did not design
inherited (three previous database maintainers in last 18 months),
Non-existent comments for existing code modules and objects, six
users on LAN, BE on shared server. Each user has own FE to allow
special report & query creation, each user has common forms for input
and edit of main table data, Main data tables are linked from BE,
special tables are stored in users FE. Default open Mode is shared;
Default Record lock is edited record.

Problem: Only one user at a time can be in database record editing
fails and second users instance of Access locks up.
Could you elablorate on the above statement?

Is the database being opened exclusively? Check the icon and see if
there is an /excl in the command line.

Or are you in a form and others can't edit?

Can you open a table, then sign into your app on another computer, and
open the same table and then try to modify a record on each PC. Does
that work?

Help needed, ideas on where to look to solve this problem welcome.
Reply in newsgroup appreciated as only check the listed email account
once a week.

Have done five Access projects on LANs but they were only on two or
three computers and always one user at a time, i.e. data entry during
day, detail reports at night, manager summary reports only no data
entry.

We are getting two additional data entry people and I need to get
this fixed, I know a real SQL Server as BE would be the best
solution, but powers that be want to stay with Access.

Can't ID where I work but computers are new Dells with Windows 2000
and MSOffice 2000, no pre-compiled code can be loaded to HD's. To
load compiled code (such as a MDE or DLL) must provide to network
manager in uncompiled format, they review then create compiled
version and push to selected computers or send a tech with a CD in
hand to load, No admin or power user rights on any user machine.

Have a nice day. ld****@NOPANTS.juno.com

Remove NOPANTS. To reply by direct E-Mail;
Support: The Right to Privacy and Anti-SPAM projects

[Thats Me]

On Sun, 30 Jan 2005 09:01:48 GMT, Salad <oi*@vinegar.com> wrote:
-------------------<reply edited>--------------------------

Thats Me wrote:

Background: Access 2000 running on Windows 2000, Did not design
inherited (three previous database maintainers in last 18 months),
Non-existent comments for existing code modules and objects, six
users on LAN, BE on shared server. Each user has own FE to allow
special report & query creation, each user has common forms for input
and edit of main table data, Main data tables are linked from BE,
special tables are stored in users FE. Default open Mode is shared;
Default Record lock is edited record.

Problem: Only one user at a time can be in database record editing
fails and second users instance of Access locks up.
Could you elablorate on the above statement?

Is the database being opened exclusively? Check the icon and see if
there is an /excl in the command line.

No "/excl in command line"

Or are you in a form and others can't edit? Yes, lock up second users instance of Access

Can you open a table, then sign into your app on another computer, and
open the same table and then try to modify a record on each PC. Does
that work?

No, will lockup one of the instances of Access

Found out today that the tried replication at one time and stopped
using it, may have some thing to do with leftovers from that fiasco.

Help needed, ideas on where to look to solve this problem welcome.
Reply in newsgroup appreciated as only check the listed email account
once a week.

Have a nice day. ld****@NOPANTS.juno.com

Remove NOPANTS. To reply by direct E-Mail;
Support: The Right to Privacy and Anti-SPAM projects

[Salad]

Thats Me wrote:

On Sun, 30 Jan 2005 09:01:48 GMT, Salad <oi*@vinegar.com> wrote:
-------------------<reply edited>--------------------------

Can you open a table, then sign into your app on another computer, and
open the same table and then try to modify a record on each PC. Does
that work?

No, will lockup one of the instances of Access

Found out today that the tried replication at one time and stopped
using it, may have some thing to do with leftovers from that fiasco.

You have a problem. That's why programmeers make "Big Bucks" :-)

Create another "junk" database in the same folder and create a junk
table and junk form. Create a desktop icon to open the mdb. Open it.
Then see if you can open another instance by clicking the icon. If you
can, then it's in your current app and not Access.

Does it lock up upon entry or when in data entry only? If so, maybe
open up a second instance that does not fire up the starting form. Then
open up the code module for a dataentry form and set the step on (click
to the left bar of the code window). Save the form, then open it.
Maybe you'll see something as you step through the code.

Good luck.

[Adil.Chaoui]

Hello Albert,
I want to start using the access but i need the initial courses to
start with for a simple programmation, that is why i'm sending you thas
message asking you help

Thanks
Rgds
Adil

[Larry Linson]

<Ad*********@dewhirst.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...

Hello Albert,
I want to start using the access but i need the initial courses to
start with for a simple programmation, that is why i'm sending you thas
message asking you help

What help, specifically, do you need?

There are online courses on many aspects of Access which you can reach from
the Office Online site,
http://office.microsoft.com/en-us/tr...829401033.aspx. Many of them
deal with just using Access, but a good understanding of using Access is
vital, because much of what we do with code is to automate functionality
that otherwise would have been done manually.

The recent thread here, entitled "Access Paper" included some
recommendations -- search for it, using http://groups.google.com. A book I
have recommended for people moving from "power user" to "developer" which
includes sections on VBA is Dr. Rick Dobson's _Programming Microsoft Access
2002_ from Microsoft Press... there is an edition of this book for Access
2000 and, if memory serves, another for Access 2003, too.

But, a suggestion: your request can get lost if you add it to a thread with
a different subject, as you did with this one. Post a new message with a
subject indicating the topic and you will have better luck getting the
answers you need. You'll find other useful suggestions for effective use of
newsgroups at the FAQ http://www.mvps.org/access/netiquette.htm.

Larry Linson
Microsoft Access MVP

[Terrell Miller]

Thats Me wrote:

Can you open a table, then sign into your app on another computer, and
open the same table and then try to modify a record on each PC. Does
that work?

No, will lockup one of the instances of Access

you may be using pessimistic locking on your forms. One user is in the
process of editing a record in a tbale, that entire table is locked
until the change is committed (i.e. the original user moves to a
diffrerent record).

You can change the locking strategy to Optimistic. Open the form in
design view, open teh form Properties window, go to the Data tab, and
set the Record Locks property to Edited Record instead of All Records.

HTH,
--
Terrell Miller
mi******@bellsouth.net

"Every gardener knows nature's random cruelty"
-Paul Simon RE: George Harrison