write create microsoft access rights?

[ryguy7272]

I saved a small Access DB, that I developed, on our firm's network drive. I
can open it and read/write just fine, but another employee can not write to
the DB. When I open it on her machine, I get a message saying: The database
is read-only. You won't be able to save the changes made to data...

Is there a setting or control that will allow full read/write rights?


Regrads,
Ryan---

 

[a a r o n . k e m p f]

SQL Server allows you to set permissions in just ONE place.. instead
of in 12 different places.

-Aaron

 

[ryguy7272]

Wow! So only one person is allowed to make changes, for instance, to a
query? I am sort of new to the world of Access...I would have expected a lot
more control and a lot less restriction from Access. I really developed this
DB for someone other than myself to do some rather sophisticated queries.
How do I transfer permission to another person?

Regards,
Ryan--

 

[George Nicholson]

Feel free to ignore Aaron. He is the neighborhood troll and just as likely
to provide misinformation as enlightenment (and that's being generous).

Does the user have full read/write/delete privileges to the network
location?

Is you have multiple people using the db at the same time, is your db
properly split between *local* Frontend (forms, reports, queries) and shared
network backend?

 

[ryguy7272]

In terms of the network, yes, full access.

As for the the other question...I don't really know what that means. I'm
learning Access as I go. I have a few books, which are helpful, but as far
as I can tell, none describe what to do in this scenario. Right now,
everything is reported in Excel. I'm quite proficient with Excel, VBA, etc.,
but I'm new to this Access stuff. Can you post a link here, which may
describe what to do in this type of scenario? I just developed the DB with
one table, I have a Form, with code, that allows a user to create some pretty
cool Reports on the fly. I also have a Form that SHOULD allow a user to
create some pretty cool Queries on the fly (with SQL, etc. passed by the Form
to the Query). This specific Query is the one that is a PITA right now. I
can't create any queries except on my own machine. The 'table' that I am
referencing is actually a link to a single sheet in an Excel workbook. If
you have a suggestion please post back. I'd be very surprised if Access
doesn't permit me to do what I am trying to do... It may be a little complex
for me, but I'd bet it is a piece of cake for for some Access MVPs out there.

Regards,
Ryan--

 

[BruceM]

Users need read/write permissions to the folder in which the mdb or mde file
is located. Access creates a lock file (ldb) during an Access session, and
deletes it when you end the session, which is why read/write permissions are
needed.

 

[ryguy7272]

One of the IT guys here fixed it for me:
Right-Click > Properties > Security > Users > then check Full Control.

This just happened by default. I've worked with both Word and Excel, for a
very long time, and I've never seen this before. I've worked with Access for
only 6-months or so, but I've never seen this before.

Thanks to everyone for looking...

Regards,
Ryan---

 

[BruceM]

Oops. This was already covered. I guess it had been a while since my
newsreader downloaded new messages.

 

[a a r o n . k e m p f]

yes; that is correct.

In an Access Database; only one person is allowed to change queries--
due to a poor design. Access databases are a decade obsolete-- it is
no longer reccomended for new people to grow into Access.

It is reccomend that anyone- that wants to learn about databases-
should go and take a class about SQL Server.

With SQL Server; you can build and share queries in between users.
This concept is called 'code reuse'-- and it is not possible with
Microsoft Access.

-Aaron

 

[a a r o n . k e m p f]

Feel free to ignore George. He is the neighborhood troll and just as
likely
to provide misinformation as enlightenment (and that's being
generous).

Have you upgraded to SQL Server yet?

If you have multiple people using the db at the same time, you should
move to SQL Server.

 

[a a r o n . k e m p f]

PS - the MVPs around here are neither
MOST
or
VALUABLE
or
PROFESSIONALS

All the so-called MVPs around here.. are stuck in a sinking boat--
that has been obsolete for a decade.
These guys around here-- consistently post incorrect information
about SQL Server.

MS Access just involves work arounds and limits--
It does not make sense for new people to get into Access.

SQL Server is easier, faster, more powerful.

SQL Server has overtaken MS Access as the database of choice for small
and medium businesses.

 

[George Nicholson]

Have you upgraded to SQL Server yet?

Yep. And I recommend either Access or SQLS solutions, depending on my
clients requirements rather than on a personal bias that has no basis in
anyone's reality except your own.

--
HTH,
George


message
Feel free to ignore George. He is the neighborhood troll and just as
likely
to provide misinformation as enlightenment (and that's being
generous).

Have you upgraded to SQL Server yet?

If you have multiple people using the db at the same time, you should
move to SQL Server.

 

[a a r o n . k e m p f]

Yes.. well you do your clients a dis-service.

Forcing them-- to eat out of your hand-- so that you can run Compact +
Repair once a month?

It's just not a good solid business practice.

Nobody should be using MDB for any reason whatsoever.

It is a dead format.

Sorry-- I won't budge from that.

-Aaron

 

[a a r o n . k e m p f]

there is no such thing as a personal bias.

There is the RIGHT database.
and everywhere else there is crap.

If you use MDB for anyhting.. then you're 'not good enough with SQL
Server'.

MDB / JET / ACCDB has _ZERO_ benefit in ease of use over SQL Server.
Unless you're some old dude that doesn't have the mental capability to
learn a new library once a decade.

 

[So Sorry For Poor Aaron]

yes; that is correct. In an Access Database; only one person is allowed

to change queries -- due to a poor design.

In an Access database, you must open for exclusive use to modify database
objects; this is to prevent one user from interfering with another's changes.
Aaron is the "kid" around here, and he doesn't know jack about Access nor
about SQL Server.

Access databases are a decade obsolete-- it is
no longer reccomended for new people to grow into Access.

Poor Aaron, the only time value he has been able to learn is "decade" -- but
it will take him longer than that to learn as much about SQL Server as he
thinks he knows, even if he spends full-time in training. Access databases,
more properly called Jet databases, not only have not been obsolete for a
decade they are not obsolete now, and just to show the value, Microsoft
created from the Jet database engine a very capable new database engine,
named ACE, for Access 2007.

It is reccomend that anyone- that wants to learn about databases-
should go and take a class about SQL Server.

Aaron's "It is recommended..." only means "Aaron recommends..."
Knowledgeable database consultants, developers, and administrators recommend,
use an appropriate database for your needs (and that includes Access), and
learn that one.

With SQL Server; you can build and share queries in between users.
This concept is called 'code reuse'-- and it is not possible with
Microsoft Access.

Aaron exposes his ignorance once more -- Access "saved queries" can be and
often are shared between users. He doesn't know jack about "code reuse",
either.

What does he know jack about? Orange jumpsuits and Big Bubba who's in the
same cell, just waiting for Aaron to come back. Big Bubba just loves orange
jumpsuits and kids like Aaron -- he doesn't care if Aaron doesn't know jack
about databases.

 

[George]

Of course, you're fully prepared to enumerate all 12 places?


message
SQL Server allows you to set permissions in just ONE place.. instead
of in 12 different places.

-Aaron

 

[George]

I just wanted to add my support to what you've learned here today and to
suggest that the reasons for the more sophisticated permissions required to
work with Access as opposed to Word or Excel make sense when you think about
what you are doing with the tools.

Access allows two or more people to work with data in the same mdb at the
same time. E.g. one person can be updating sales records in one table, while
a different person is adding new employee records in a different tables. In
order to minimize conflicts between multiple users, Access needs to know who
all has the database open. It does that by creating a small locking file,
with an extension of .ldb. The ldb file has the same name as the database
file.

"SalesTracking.mdb", for example, will create a "SalesTracking.ldb" file
when the FIRST person opens the mdb. The ldb file resides in the same folder
as the mdb. Whenever another person opens that mdb, their user information
is appended to the data in the ldb, so that Access can track both users.
From then on, each new user opening the mdb is also added to the ldb.

Then, as users close their copy of the mdb, the ldb tracks their exit as
well. When the LAST user closes their copy of the mdb, Access deletes that
ldb. Of course, the next time someone opens the mdb, a new ldb gets created.

Because any user who tries to open the mdb must be able to create or delete
the corresponding ldb, as described above, Access required that they have
read/write permissions on the folder in which the mdb resides.

You can see somewhat similar behavior in Excel when two people try to open
the same Excel workbook. Unless the first user shares the workbook, the
second (or additional) user will be shown a dialog telling them that the
workbook can be opened Read-Only, or that the second person can wait to be
notified when the workbook is available for editing.

Similar goal, different approach.

Don't be misled by references to SQL Server, which, while possibly true, are
irrelavent to what you need.

 

[So Sorry For Poor Aaron]

Aaron can't, sir, but I can -- all 12 are in the empty space between aaron's
ears, where his brain used to be before he burned it out.

Of course, you're fully prepared to enumerate all 12 places?

to aaron.kempf, who had claimed:

 

[a a r o n . k e m p f]

yah..

NTFS ReadPerms for FrontEnd
NTFS ReadPerms for BackEnd
NTFS ReadPerms for TempDbEnd

NTFS WritePerms for FrontEnd
NTFS WritePerms for BackEnd
NTFS WritePerms for TempDbEnd

NTFS ExecutePerms for FrontEnd
NTFS ExecutePerms for BackEnd
NTFS ExecutePerms for TempDbEnd

NTFS DeletePerms for FrontEnd
NTFS DeletePerms for BackEnd
NTFS DeletePerms for TempDbEnd

JET Workgroup ReadPerms for FrontEnd
JET Workgroup ReadPerms for BackEnd
JET Workgroup ReadPerms for TempDbEnd

JET Workgroup WritePerms for FrontEnd
JET Workgroup WritePerms for BackEnd
JET Workgroup WritePerms for TempDbEnd

JET Workgroup FormPerms for FrontEnd
JET Workgroup QueryPerms for FrontEnd
JET Workgroup ReportPerms for FrontEnd


I mean.. do I really need to continue?

-Aaron

 

[a a r o n . k e m p f]

oh wah!! someone is making up names and chasing me online!!

WAHHHHHHHHHHHHHHHHHHHHH!!!!!!!

Access 'saved queries' can _NOT_ be shared between users.
Two different people can not write queries at the same time and share
them.

Anything else sounds like a PITA to me.

I know plenty more about SQL Server than anyone else on this group..
and for the most part I'm probably better with Access than 99.999 %
people around here.

Just because I'm unpopular around here-- that doesn't mean that I'm
wrong.
It just means that the database retards can't get their way any
longer.

Some dipshit MVP said THREE incorrect things in a single post.

I'll gladly reccomend SQL Server where I see fit.

Access didn't 'create a new version'--- they brought it back from the
DEAD.
Just because it WAS a dead database.. and it's not now-- that doesn't
mean that it's not a dead database.

It just means that they delayed killing it off.

SQL Server slaughters Access in every category-- _ESPECIALLY_ price
and ease of development.

If anyone else tries to tell you otherwise.. they are trying to sell
you some worthless obsolete JET crap.

-Aaron