New users cannot edit

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have new employees that can edit in some forms of our database, but not in
others. There are no levels of security on the server or in the database and
it seems to be only affecting new employees. Is there anyone who knows how
to fix this problem?

I can be reached at (e-mail address removed). Thank you very much.
 
Roger,

That was one of the first things I tried. Thanks very much for your response.
--
Cindy



Roger Carlson said:
Make sure all of these new users have ALL network rights to the Folder where
the database resides. You'll have to talk to your network administrator to
do this.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
btw; if you used Access Data Projects you wouldn't need to setup
security in 9 different places.

with MDB you have to set NTFS; workgroup security and application
security (internal homegrown code that keeps you out of certain tables
for example)

MDB is comical and obsolete; use Access Data Projects
 
Hummmm. I would have bet good money that Roger was right.

What do you mean by "New users cannot edit"? Do they get error messages? Are
the areas where they try to edit grayed out? Possibly as new users they are
trying to edit records in a why experience users wouldn't?
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


Cindy said:
Roger,

That was one of the first things I tried. Thanks very much for your response.
 
Jerry;

if you lost the training wheels you wouldn't have to make your
customers choose between light; cheap and strong.

I deliver all 3 with Access Data Projects.

-Aaron
 
Thanks Jerry. I would have bet he was right, too, but it has my IT
Department (the keeper of the server) stumped. I have gone into their
computer under my user name and was able to open the db and edit. It is only
under their name that it doesn't allow. What is stranger is that some places
in the db lets them edit and others do not. They do not get any error
messages, but the records are locked from editing. I built the database in
2000 and didn't set any securities on the db, forms, etc. That is why I have
turned to the experts because I am at the end of my knowledge. I hope this
makes sense.
 
I'm still betting that Roger is right. Doube, no triple, check that all users
have read, write, create, and delete privileges to the folder holding the
database. Not just the .mdb file but the entire folder.

Try this: make sure that everyone is out of the database by going to the
folder holding it. There should not be a .ldb file of the same name in the
folder. Have one of the problem users open the database. Is an .ldb file
created? If not, the user doesn't have create privs in that folder. Probably
not the other 3 needed privs also.

Speaking of .ldb files, when everyone is out of the database, check to see
if a .ldb file remains. If it does, delete it and see if the problem goes
away as least for a while. If users don't have delete privs, that can cause a
..ldb file to hang around and cause problems. Also if someone or something
causes the database to shut down incorrectly the .ldb file might stay around
and cause problems.
 
yeah.. because MDB is a flaky ass technology and anyone using it
anywhere should be fired on the spot.

it has NO BENEFIT over Access Data Projects.. except more maintenance
dollars for you crappy ass sloppy ass developers

keep everything in one database; views; sprocs-- sprocs are 100 times
more powerful than your silly trivial mdb queries

****ing pansies all dressed in pink

ROFL
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top