编辑FE时,DB慢速爬行 [英] DB Slows to a crawl when editing FE

查看:86
本文介绍了编辑FE时,DB慢速爬行的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的数据库上有FE / BE设置。



这样做的主要原因之一就是我可以编辑前端并上传它而不会导致一天出现问题到日活动。


我让它满足于用户组的安全性,所以每个人都必须登录。

我有一个单独的FE我编辑的变化,但BE数据仍然指向

。我的问题是,当我登录到数据库以进行编辑时,即使我使用的是单独的FE而非活动用户,

数据库也会慢慢爬行除非每个人都退出。在编辑任何内容时,操作之间需要几分钟






我已经尝试制作数据库副本并剥离所有表格

out,但是当我从中导入表格并重新启动数据库时

崩溃。我还尝试将表格导回到FE中,这样我就可以编辑所以表格实际存在了,但是我有相同的结果

结果;当我将表格导入工作数据库时,它会崩溃。


我做错了什么?这是一个常见的

问题吗?有没有人知道解决方法或解决这个问题?


我为交叉发布道歉。我确实在cdma.Forms发布了这个问题

上周五,但只得到一个回复​​而且它没有帮助。


任何建议都会很大赞赏。

I have a FE / BE setup on my database. One of the main reasons that
I
did this was so that I could edit the front end and upload it without
causing problems with day to day activities.

I have it sat up with user group security so everyone has to log in.
I have a seperate FE that i edit changes in, but it is still pointed
at the BE data. My problem is that when i log into the database to
edit it, even though i''m using a seperate FE than active users, the
database slows to a crawl unless everyone logs out. It takes minutes
between actions
when editing anything.

I''ve tried making a copy of the DB and stripping all of the tables
out, however when i import forms from it and restart the DB it
crashes. I''ve also tried importing the tables back into the FE that
i''m editing so the tables are actually there, but i have the same
results; when i import the forms into the working DB it crashes.

Am I doing something wrong? Is this a common
problem? Does anyone know of a work around or solution to this?

I apologize cross posting. I did post this problem in c.d.ma.Forms
last friday but only got one response and it didn''t help.

Any suggestions would be greatly appreciated.

推荐答案

1月8日下午12:08,Snoopy33< holland ... @ hotmail.comwrote:
On Jan 8, 12:08 pm, Snoopy33 <holland...@hotmail.comwrote:

我让它满足于用户组的安全性所以每个人都必须登录。

我有一个单独的FE,我编辑了变化,但是BE数据仍然指向

。我的问题是,当我登录到数据库以进行编辑时,即使我使用的是单独的FE而非活动用户,

数据库也会慢慢爬行除非每个人都退出。在编辑任何内容时,操作之间需要几分钟




I have it sat up with user group security so everyone has to log in.
I have a seperate FE that i edit changes in, but it is still pointed
at the BE data. My problem is that when i log into the database to
edit it, even though i''m using a seperate FE than active users, the
database slows to a crawl unless everyone logs out. It takes minutes
between actions
when editing anything.



确保您的FE链接指向C盘上的链接。

make sure your FE link is to the one on the C drive.


我已经尝试制作数据库的副本并剥离所有表格

out,但是当我从中导入表单并重新启动数据库时

崩溃。我还尝试将表格导回到FE中,这样我就可以编辑所以表格实际存在了,但是我有相同的结果

结果;当我将表单导入工作DB时,它崩溃了。
I''ve tried making a copy of the DB and stripping all of the tables
out, however when i import forms from it and restart the DB it
crashes. I''ve also tried importing the tables back into the FE that
i''m editing so the tables are actually there, but i have the same
results; when i import the forms into the working DB it crashes.



所有的桌子都在BE中,你的所有表格都在FE中?


all of your tables are in the BE and all your forms are in the FE?


Snoopy33写道:
Snoopy33 wrote:

我的数据库中有FE / BE设置。



这样做的主要原因之一就是我可以编辑前端并上传它而不会导致一天出现问题到日活动。


我让它满足于用户组的安全性,所以每个人都必须登录。

我有一个单独的FE我编辑的变化,但BE数据仍然指向

。我的问题是,当我登录到数据库以进行编辑时,即使我使用的是单独的FE而非活动用户,

数据库也会慢慢爬行除非每个人都退出。在编辑任何内容时,操作之间需要几分钟






我已经尝试制作数据库副本并剥离所有表格

out,但是当我从中导入表格并重新启动数据库时

崩溃。我还尝试将表格导回到FE中,这样我就可以编辑所以表格实际存在了,但是我有相同的结果

结果;当我将表格导入工作数据库时,它会崩溃。


我做错了什么?这是一个常见的

问题吗?有没有人知道解决方法或解决这个问题?


我为交叉发布道歉。我确实在cdma.Forms发布了这个问题

上周五,但只得到一个回复​​而且它没有帮助。


任何建议都会很大赞。
I have a FE / BE setup on my database. One of the main reasons that
I
did this was so that I could edit the front end and upload it without
causing problems with day to day activities.

I have it sat up with user group security so everyone has to log in.
I have a seperate FE that i edit changes in, but it is still pointed
at the BE data. My problem is that when i log into the database to
edit it, even though i''m using a seperate FE than active users, the
database slows to a crawl unless everyone logs out. It takes minutes
between actions
when editing anything.

I''ve tried making a copy of the DB and stripping all of the tables
out, however when i import forms from it and restart the DB it
crashes. I''ve also tried importing the tables back into the FE that
i''m editing so the tables are actually there, but i have the same
results; when i import the forms into the working DB it crashes.

Am I doing something wrong? Is this a common
problem? Does anyone know of a work around or solution to this?

I apologize cross posting. I did post this problem in c.d.ma.Forms
last friday but only got one response and it didn''t help.

Any suggestions would be greatly appreciated.



查看Tony Toew的网站。
http://www.granite.ab.ca/access/splitapp/index.htm


使我的应用程序变慢的那个是长文件名。例如:

\TestApplication\Junk.mdb。如果它是\ Test \ Jun.mdb更好。

Check out Tony Toew''s site.
http://www.granite.ab.ca/access/splitapp/index.htm

The one that made my app slow was long file names. Ex:
\TestApplication\Junk.mdb. Better if it were \Test\Junk.mdb.


正如其他人推荐的那样,保留FE和BE的开发副本

在本地硬盘驱动器上的开发目录中。然后将

本地FE链接到本地​​BE以进行编辑。一旦yoru准备好了b / b $ b发布新的FE重新链接到实时数据并将其发送给每个

用户。我假设您没有错误地允许所有用户使用
来处理FE的单个副本。如果你是的话,现在给自己一个很大的好处,然后搜索NG为什么你不应该这样做。基本上

不是因为你的数据被破坏了,而是什么时候。
As others have recommended, keep a development copy of the FE and BE
in a Development directory on your local hard drive. Then link the
local FE to that local BE to do your edits. Once yoru are ready to
publish the new FE relink to the live data and send it out to each
user. I assume you are not making the mistake of allowing all users
to work with a single copy of the FE. If you are, do yourself a big
favor now and search the NG as to why you should not do so. Basically
it is not a matter of IF your data gets corrupted but WHEN.


这篇关于编辑FE时,DB慢速爬行的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆