拆分数据库 - Citrix - 共享前端问题 [英] Split database - Citrix - shared front end question
问题描述
我有一个拥有拆分数据库（前端/后端）的客户端。他们
也使用Access安全性 - MDW文件。前端MDE文件，
后端MDB文件和MDW文件都位于文件服务器上的共享
文件夹中。他们有两个用户群 - 本地
和远程用户。 *所有*用户目前通过Citrix
登录进入系统。他们登录Citrix并获得Citrix桌面。然后他们
通过Citrix桌面上的快捷方式启动应用程序。但是，
Citrix桌面上的快捷方式只指向文件服务器上的共享前端
MDE文件。换句话说，他们没有向所有本地用户桌面和Citrix
服务器发布前端
。
他们目前有很多腐败问题，其中
系统告诉他们MDW文件已损坏。然后他们从系统中获取每个人的
并用备份的
副本替换MDW文件。
他们是也有定期问题，Access报告它无法在文件服务器共享上找到MDE文件。如果他们保持
尝试它，最终（可能是一两分钟）他们可以正常打开
。
我认为他们需要将前端MDE文件分发到所有本地桌面的
，然后将前端MDE文件移动到Citrix服务器的
所以它是Citrix服务器的本地服务器。我不是
确切知道Access打开后幕后发生了什么
就网络流量而言我的预感是他们目前的设置
有很多不必要的网络流量。
任何想法或评论都会有所帮助。
谢谢，
Corey Burnett
我以同样的方式使用Citrix。在每个用户中放置前端的副本
Citrix服务器上的主目录。请记住，您必须将每个Citrix
用户视为运行PC。
我的所有用户都有一个驱动器号I：映射到用户目录，就这样
这些捷径看起来都一样。
" Corey Burnett" <第********* @ yahoo.com>在消息中写道
news：73 ************************** @ posting.google.c om ...我的客户端有一个拆分数据库（前端/后端）。他们还使用Access安全性 - MDW文件。前端MDE文件，后端MDB文件和MDW文件都位于文件服务器上的共享
文件夹中。他们有两个用户群 - 本地用户和远程用户。 *所有*用户目前通过Citrix
登录进入系统。他们登录Citrix并获得Citrix桌面。然后他们通过Citrix桌面上的快捷方式启动应用程序。但是，Citrix桌面上的快捷方式只指向文件服务器上的共享前端
MDE文件。换句话说，他们没有将前端分发给所有本地用户桌面和Citrix
服务器。
他们目前有很多腐败问题，其中
系统告诉他们MDW文件已损坏。然后他们将所有人从系统中取出并用备份的
副本替换MDW文件。
他们也有定期问题，其中Access报告它
无法在文件服务器共享上找到MDE文件。如果他们继续尝试，最终（可能是一两分钟）他们可以正确地打开它。
我在想他们需要分发前端MDE文件到所有本地桌面，然后还将前端MDE文件移动到Citrix服务器，使其成为Citrix服务器的本地服务器。我不确定在网络流量方面打开Access后幕后发生的事情，但我的预感是他们目前的设置
有很多不必要的网络流量。
任何想法或评论都会有所帮助。
谢谢，
Corey Burnett
< blockquote>从它的声音 - 问题''发现''访问文件和
腐败 - 似乎有一些网络问题 - 要么
慢/过度使用网络，丢失数据包等。
最简单的解决方法是将所有文件本地化到Citrix
服务器。
通过拥有Citrix服务器上的所有文件，您可以获得所有文件本地化的价格，并保持相同的支持级别 - 所有这些你所有的
进行升级必须升级Citrix
服务器上的访问文件。如果你将文件分发给每个用户工作站，你将会遇到支持问题。
th ********* @ yahoo.com （Corey Burnett）在留言中写道：< 73 *********** ***************@posting.google。 com> ...
我的客户端有一个拆分数据库（前端/后端）。他们还使用Access安全性 - MDW文件。前端MDE文件，后端MDB文件和MDW文件都位于文件服务器上的共享
文件夹中。他们有两个用户群 - 本地用户和远程用户。 *所有*用户目前通过Citrix
登录进入系统。他们登录Citrix并获得Citrix桌面。然后他们通过Citrix桌面上的快捷方式启动应用程序。但是，Citrix桌面上的快捷方式只指向文件服务器上的共享前端
MDE文件。换句话说，他们没有将前端分发给所有本地用户桌面和Citrix
服务器。
他们目前有很多腐败问题，其中
系统告诉他们MDW文件已损坏。然后他们将所有人从系统中取出并用备份的
副本替换MDW文件。
他们也有定期问题，其中Access报告它
无法在文件服务器共享上找到MDE文件。如果他们继续尝试，最终（可能是一两分钟）他们可以正确地打开它。
我在想他们需要分发前端MDE文件到所有本地桌面，然后还将前端MDE文件移动到Citrix服务器，使其成为Citrix服务器的本地服务器。我不确定在网络流量方面打开Access后幕后发生的事情，但我的预感是他们目前的设置
有很多不必要的网络流量。
任何想法或评论都会有所帮助。
谢谢，
Corey Burnett
< blockquote>我在原帖中忽略了一件事，那就是有许多负载均衡的Citrix服务器 - 而不仅仅是一台。因此，虽然我可以将前端数据库移动到Citrix服务器上，但我无法移动
后端数据库和MDW文件。另外，我们假设我们有50个b $ b用户和4个Citrix服务器。然后我想我必须将
前端MDE文件复制到所有4个
Citrix服务器上的所有50个用户配置文件主目录 - 200个MDE文件副本。我理解这个
正确吗？所以我可以消除一些网络流量，但不是所有的b $ b。
***通过Developersdex发送 http://www.developersdex.com ***
不要只参加USENET。 ..得到奖励！
I have a client that has a split database (front-end/back-end). They
are also using Access security - MDW file. The front end MDE file,
the back end MDB file, and the MDW file are all located on a shared
folder on the file server. They have two populations of users - local
and remote. *ALL* users currently get to the system via a Citrix
login. They log in to Citrix and get a Citrix desktop. Then they
start the application via a shortcut on their Citrix desktop. However
the shortcut on the Citrix desktop just points to the shared front-end
MDE file on the file server. In other words they have not distributed
the front end to all of the local user desktops and to the Citrix
server.
They are currently having a lot of corruption problems where the
system tells them that the MDW file is corrupt. They then get
everyone out of the system and replace the MDW file with a backed-up
copy.
They are also having periodic problems where Access reports that it
can''t locate the MDE file on the file server share. If they keep
trying it, eventually (maybe a minute or two) they can get it to open
up correctly.
I am thinking that they need to distribute the front end MDE file to
all of the local desktops and then also move the front end MDE file to
the Citrix server so that it is local to the Citrix server. I am not
real sure of what is going on behind the scenes when Access is opened
in terms of network traffic but my hunch is that their current set up
has a lot of unnecessary network traffic.
Any ideas or comments would be helpful.
Thanks,
Corey Burnett
I am using Citrix in the same way. Put a copy of the front-end in each user
Home directory on the Citrix server. Remember you must treat each Citrix
user as if they are running a PC.
All my users have a drive letter I: mapped to the user directory, That way
the short cuts all look the same.
"Corey Burnett" <th*********@yahoo.com> wrote in message
news:73**************************@posting.google.c om...I have a client that has a split database (front-end/back-end). They
are also using Access security - MDW file. The front end MDE file,
the back end MDB file, and the MDW file are all located on a shared
folder on the file server. They have two populations of users - local
and remote. *ALL* users currently get to the system via a Citrix
login. They log in to Citrix and get a Citrix desktop. Then they
start the application via a shortcut on their Citrix desktop. However
the shortcut on the Citrix desktop just points to the shared front-end
MDE file on the file server. In other words they have not distributed
the front end to all of the local user desktops and to the Citrix
server.
They are currently having a lot of corruption problems where the
system tells them that the MDW file is corrupt. They then get
everyone out of the system and replace the MDW file with a backed-up
copy.
They are also having periodic problems where Access reports that it
can''t locate the MDE file on the file server share. If they keep
trying it, eventually (maybe a minute or two) they can get it to open
up correctly.
I am thinking that they need to distribute the front end MDE file to
all of the local desktops and then also move the front end MDE file to
the Citrix server so that it is local to the Citrix server. I am not
real sure of what is going on behind the scenes when Access is opened
in terms of network traffic but my hunch is that their current set up
has a lot of unnecessary network traffic.
Any ideas or comments would be helpful.
Thanks,
Corey Burnett
From the sounds of it - the problem ''finding'' the access file and the
corruption - there seems to be some network issue - either a
slow/over-utilized network, lost packets, etc.
The easiest way to resolve is to localize all the files to the Citrix
server.
By having all the files on the Citrix server you can gain the speed by
having all files ''localized'' and keep the same support level - all you
have to do for an upgrade is to upgrade the access files on the citrix
server. if you distribute the files to each users workstation you''ll
run into the problem of support.
th*********@yahoo.com (Corey Burnett) wrote in message news:<73**************************@posting.google. com>...I have a client that has a split database (front-end/back-end). They
are also using Access security - MDW file. The front end MDE file,
the back end MDB file, and the MDW file are all located on a shared
folder on the file server. They have two populations of users - local
and remote. *ALL* users currently get to the system via a Citrix
login. They log in to Citrix and get a Citrix desktop. Then they
start the application via a shortcut on their Citrix desktop. However
the shortcut on the Citrix desktop just points to the shared front-end
MDE file on the file server. In other words they have not distributed
the front end to all of the local user desktops and to the Citrix
server.
They are currently having a lot of corruption problems where the
system tells them that the MDW file is corrupt. They then get
everyone out of the system and replace the MDW file with a backed-up
copy.
They are also having periodic problems where Access reports that it
can''t locate the MDE file on the file server share. If they keep
trying it, eventually (maybe a minute or two) they can get it to open
up correctly.
I am thinking that they need to distribute the front end MDE file to
all of the local desktops and then also move the front end MDE file to
the Citrix server so that it is local to the Citrix server. I am not
real sure of what is going on behind the scenes when Access is opened
in terms of network traffic but my hunch is that their current set up
has a lot of unnecessary network traffic.
Any ideas or comments would be helpful.
Thanks,
Corey Burnett
One thing I neglected to clarify in my original post was that there are
many load balanced Citrix servers - not just one. So while I could move
the front end database on to the Citrix servers, I could not move the
back end database and the MDW file. Also let''s say that we have 50
users and 4 Citrix servers. Then I guess that I will have to copy the
front end MDE file to all 50 user profiles home directory on all 4
Citrix servers - 200 copies of the MDE file. Am I understanding this
correctly? So I could eliminate some of the network traffic but not all
of it.
*** Sent via Developersdex http://www.developersdex.com ***
Don''t just participate in USENET...get rewarded for it!
这篇关于拆分数据库 - Citrix - 共享前端问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
