访问与“独占”相关的警告模式 [英] Access warnings relating to "exclusive" mode

问题描述

我最近在一家医疗人员公司找到了一份工作，一个用来保存信息的数据库是由那位访问经验非常有限（甚至比我少）的女士建造的。


他们在WinXP桌面上运行Access2k3


文件和数据库驻留在公司服务器上。


她抱怨早上第一个人谁打开数据库锁定所有其他人，一旦他们退出，其他人登录每个人都可以开始工作。

通过研究我认为第一个人打开数据库的独家模式因此锁定所有其他人。


1.我如何解决这个锁定问题。问题？


一些研究表明，数据库数据应该驻留在服务器上，而前端则应该存在。应该驻留在各个工作站上。


2.事后可以做些什么吗？


另一个问题是警告框...


*** Microsoft Office访问权限无法保存设计更改或保存到新的数据库对象，因为另一个用户打开了该文件。要保存设计更改或保存到新对象，您必须具有对文件的独占访问权。***


3.数据库用户和组架构的实现是否有帮助事情？

例如，设置一个数据库管理员并将其他人设置为用户。


我在网上做的研究论坛有点帮助，但大部分都在我头上


提前感谢任何帮助......

I recently started a job at a medical staffing company, a database used to keep information was built by a lady there who has very limited Access experience (even less than me)

They run Access2k3, on WinXP desktops

The files and DB reside on the corporate server.

She complains that in the mornings the first person who opens the DB locks all others out, once they logout and the others log in everyone can begin working.
Through research I figure that the first person is opening the DB in "exclusive" mode therefore locking all others out.

1. How can I fix this "lockout" problem?

Some research says that the DB data should reside on the server, while the "frontend" should reside on the individual workstations.

2. Is this something that can be done after the fact?

Another problem is the caution box...

***Microsoft office access cant save design changes or save to a new database object because another user has the file open. To save your design changes or to save to a new object, you must have exclusive access to the file.***

3. Would the implementation of a DB users and groups schema help things?
For instance, setting having one DB admin and having the rest of the others set up as users.

The research I did online and in this forum helps a little, but most of it is over my head

Thanks in advance for any help...

推荐答案

我最近在一家医疗人员公司找到了一份工作，一个用来保存信息的数据库是由那位访问经验非常有限（甚至比我少）的女士建造的。 />

他们在WinXP桌面上运行Access2k3


文件和数据库驻留在公司服务器上。


她抱怨说，在早上，第一个打开数据库的人锁定所有其他人，一旦他们退出，其他人登录我n每个人都可以开始工作了。

通过研究我认为第一个人在独家中打开数据库。模式因此锁定所有其他人。


1.我如何解决这个锁定问题。问题？


一些研究表明，数据库数据应该驻留在服务器上，而前端则应该存在。应该驻留在各个工作站上。


2.事后可以做些什么吗？


另一个问题是警告框...


*** Microsoft Office访问权限无法保存设计更改或保存到新的数据库对象，因为另一个用户打开了该文件。要保存设计更改或保存到新对象，您必须具有对文件的独占访问权。***


3.数据库用户和组架构的实现是否有帮助事情？

例如，设置一个数据库管理员并将其他人设置为用户。


我在网上做的研究论坛有点帮助，但大部分都在我头上


提前感谢您的帮助......

I recently started a job at a medical staffing company, a database used to keep information was built by a lady there who has very limited Access experience (even less than me)

They run Access2k3, on WinXP desktops

The files and DB reside on the corporate server.

She complains that in the mornings the first person who opens the DB locks all others out, once they logout and the others log in everyone can begin working.
Through research I figure that the first person is opening the DB in "exclusive" mode therefore locking all others out.

1. How can I fix this "lockout" problem?

Some research says that the DB data should reside on the server, while the "frontend" should reside on the individual workstations.

2. Is this something that can be done after the fact?

Another problem is the caution box...

***Microsoft office access cant save design changes or save to a new database object because another user has the file open. To save your design changes or to save to a new object, you must have exclusive access to the file.***

3. Would the implementation of a DB users and groups schema help things?
For instance, setting having one DB admin and having the rest of the others set up as users.

The research I did online and in this forum helps a little, but most of it is over my head

Thanks in advance for any help...

__1工具==>选项==>高级==>默认打开模式=共享

__2数据本身（表）应驻留在服务器上，而应用程序对象（表单，宏，报告，查询，模块）驻留在客户端PC上。然后将这些前端DB（客户端）链接到驻留在服务器上的后端数据库。多个用户现在可以访问现在存在于后端数据库（服务器）上的集中式数据源。从单个数据库创建前端和后端数据库肯定可以在事后完成。

__3生活中一个简单的事实是某些设计更改只能在数据库以独占模式打开（非多用户访问）。为此，==>打开Microsoft Access ==> File =>打开==>选择要打开的数据库==>点击打开按钮上的小箭头==>选择Open Exclusive。

__4数据库现在将以独占模式打开。进行任何必要的设计更改然后退出。按照惯例继续进行。

__5如果您有任何其他问题，请随时询问。

__1 Tools ==> Options ==> Advanced ==> Default Open mode = Shared
__2 The Data itself (Tables) should reside on the Server, while the Application Objects (Forms, Macros, Reports, Queries, Modules) reside on the Client PCs. These Front End DBs (Clients) are then Linked to the Back End Database residing on the Server. Multiple Users can now access a centralized Data Source that now exists on a Back End Database (Server). The creation of Front and Back End Databases from a single Database can definately de done ''after the fact''.
__3 It is a simple fact of life that certain design changes can only be implemented while a Database is opened in Exclusive Mode (non Multiuser access). To do this, ==> open Microsoft Access ==> File => Open ==> select Database to Open ==> click on little arrow on Open button ==> select Open Exclusive.
__4 The Database will now be Open in Exclusive Mode. Make any necessary Design changes then exit. Proceed as you normally would.
__5 Should you have any other questions, feel free to ask.

感谢您的及时回复......

如果我将默认的open方法更改为shared，那么我有多大信心？我不会搞砸他们的数据库，我只是担心，因为我刚刚开始。我知道全国有多个诊所都登录到数据库，他们都在分布式文件系统上，但我很确定传播数据库的所有数据都只驻留在服务器上。如果我将默认打开模式更改为共享，这个结构是否会对DB产生负面影响？


就前端/后端而言，我理解整个数据库（表单和数据）驻留在服务器上。如果我要将它拆分，究竟会出现在他们的桌面PC上（前端）？什么会在后端？我看了你的帖子，但我觉得我对措辞的确切性质感到有点困惑。数据库由表单组成，这是数据所在的位置，那么前端会是什么？


在我研究如何拆分它时你能想到任何在进行拆分之前我应该​​获得相关信息吗？


如果我要为数据库设置权限模式，这可能会解决有时无法写入数据的问题吗？或者这两个不同的主题是什么？


再次感谢您的帮助

Thanks for the prompt reply...
So how confident can I be that if I change the default open method to "shared" that I won''t mess up their DB, i''m just worried because I just started there. I know that there are multiple clinics across the country which all login to the DB and they are all on a distributed file system, but i''m pretty sure that all of the data propogating the DB resides only on the server. Could this structure impact the DB adversely if I changed the default open mode to "shared"?

As far as the front end/back end thing, as I understand it the entire DB (forms, and data) reside on the server. If I were to split it up, what exactly would reside on their desktop PC''s (front-end)? What would be on the back-end? I read your post but I think I am a bit confused about the exact nature of the wording. The DB is made up of forms, which is where the data resides, so what would be the front-end?

During my research on how to split it up can you think of any pertinent information I should obtain before going through with the split?

If I were to set up a permissions schema for the DB could this possibly take care of the problem of the data sometimes not being written? Or are these two different topics?

Thanks again for the help

感谢及时回复...

如果我将默认的open方法更改为shared，那么我有多大信心我不会搞砸他们的数据库，我只是担心，因为我刚刚开始。我知道全国有多个诊所都登录到数据库，他们都在分布式文件系统上，但我很确定传播数据库的所有数据都只驻留在服务器上。如果我将默认打开模式更改为共享，这个结构是否会对DB产生负面影响？


就前端/后端而言，我理解整个数据库（表单和数据）驻留在服务器上。如果我要将它拆分，究竟会出现在他们的桌面PC上（前端）？什么会在后端？我看了你的帖子，但我觉得我对措辞的确切性质感到有点困惑。数据库由表单组成，这是数据所在的位置，那么前端会是什么？


在我研究如何拆分它时你能想到任何在进行拆分之前我应该​​获得相关信息吗？


如果我要为数据库设置权限模式，这可能会解决有时无法写入数据的问题吗？或者是这两个不同的主题？


再次感谢帮助

Thanks for the prompt reply...
So how confident can I be that if I change the default open method to "shared" that I won''t mess up their DB, i''m just worried because I just started there. I know that there are multiple clinics across the country which all login to the DB and they are all on a distributed file system, but i''m pretty sure that all of the data propogating the DB resides only on the server. Could this structure impact the DB adversely if I changed the default open mode to "shared"?

As far as the front end/back end thing, as I understand it the entire DB (forms, and data) reside on the server. If I were to split it up, what exactly would reside on their desktop PC''s (front-end)? What would be on the back-end? I read your post but I think I am a bit confused about the exact nature of the wording. The DB is made up of forms, which is where the data resides, so what would be the front-end?

During my research on how to split it up can you think of any pertinent information I should obtain before going through with the split?

If I were to set up a permissions schema for the DB could this possibly take care of the problem of the data sometimes not being written? Or are these two different topics?

Thanks again for the help

将开放模式更改为共享不应影响数据库不利，但正如常识所要求的那样，始终在启动任何更改之前备份您的数据。


简而言之，只有表（数据）将驻留在后端，而表单，宏，模块，报告和查询将驻留在前端。


我不感谢数据库权限与周期性未写入数据的问题有关。它似乎是一些其他无关的问题。

Changing the Open Mode to Shared should not affect the Database adversely, but as common sense would dictate, always backup yourr Data before initiating any changes.

In short, only Tables (data) would reside on the Back End, while Forms, Macros, Modules, Reports, and Queries would reside on the Front Ends.

I do not thank Database Permissions relate to the problem of data periodically not being written. It appears to be some other, unrelated, problem.

这篇关于访问与“独占”相关的警告模式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！