DB Slows to a crawl when editing FE

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.

Re: DB Slows to a crawl when editing FE

On Jan 8, 12:08 pm, Snoopy33 wrote:

> 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.

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


> 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.


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

Re: DB Slows to a crawl when editing FE

Snoopy33 wrote:

> 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.
>
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.

Re: DB Slows to a crawl when editing FE

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.

Re: DB Slows to a crawl when editing FE

Thanks for all the responses.

Yes, All 61 tables are in the BE and all forms are on the FE.

I'm using the autoFEupdater that I downloaded at Tony Toew's site.
It's excellent. It allows everyone to store a copy of the FE on their
local computer and download the updated copy only if it's been
updated.

the path to my db is r:\rma\system\edit ' Storage for copy i'm
working on
\Save ' storage
for saved copy before updating to new FE
\BE ' Storage
for BE
\rev ' Storage
for current revision

the database name is RMA.mdb. I don't think the problem is too long a
path or Dir names.

I'll try what you suggested as far as keeping a local BE directory and
then relinking to the working BE when updating.

The only problem that I see is in relinking all 61 tables while
everyone is logged in, although I can make changes and stay after
everyone leaves or get there early in the morning to upload the
changed copy. This would at least allow me to freely make changes
during the work day.

Re: DB Slows to a crawl when editing FE

frogsteaks@yahoo.com wrote:

> 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.

Additionally,
Tools/Addins/Linked Table Manager (A97)
Tools/DatabaseUtilities/Linked Table Manager (2000+)

Use File/GetExternalData/Link when you add a new table to the BE.

Re: DB Slows to a crawl when editing FE

I've created local FE and BE directories and changed the links on my
FE to point to the local one. as an experiment, I tried to relink the
DB while i had about half a dozen people logged in. I thought it
locked up and had to cancel the operation and do an end task, however
when i brought it back up, it appeared to have relinked several of the
tables to the Live BE. I guess patience would have been the
rule :D .

I still believe it will be more prudent to wait until the evening when
everyone leaves or morning before anyone logs on to relink and upload
changes, but this does give me a work around to my original problem of
not being able to edit during the day.

Thanks to everyone who responded. All responses were useful.

Ben

Re: DB Slows to a crawl when editing FE

User level security? Make sure you use a separate copy of
the MDW while doing design work. Design work sometimes
locks up the the network copy of the workgroup.

(david)



"Snoopy33" wrote in message
news:4b282f9b-ac36-42c5-910d-fb685f0be393@h11g2000prf.google groups.com...
>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.
>

Re: DB Slows to a crawl when editing FE

Snoopy33 wrote:

>I've created local FE and BE directories and changed the links on my
>FE to point to the local one. as an experiment, I tried to relink the
>DB while i had about half a dozen people logged in. I thought it
>locked up and had to cancel the operation and do an end task, however
>when i brought it back up, it appeared to have relinked several of the
>tables to the Live BE. I guess patience would have been the
>rule :D .

If you are running your own relinking code then once you've relinked the first table
open a recordset against that table. Relinking the subsequent tables will go much,
much faster.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Re: DB Slows to a crawl when editing FE

Snoopy33 wrote:

>
>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.

Do you have a table, recordset or bound form open against the database while you are
editing the FE linked to the BE on a network share? This is extemely important.

Although even there I find it to be too sluggish to allow me my full productivity.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Re: DB Slows to a crawl when editing FE

On Jan 12, 2:29=A0pm, "Tony Toews [MVP]" wrote:
> Snoopy33 wrote:
>
> >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. =A0My 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. =A0It takes minutes
> >between actions
> >when editing anything.
>
> Do you have a table, recordset or bound form open against the database whi=
le you are
> editing the FE linked to the BE on a network share? =A0This is extemely im=
portant.
>
> Although even there I find it to be too sluggish to allow me my full produ=
ctivity.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> =A0 =A0Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> =A0 =A0Microsoft Access Links, Hints, Tips & Accounting Systems athttp://w=
ww.granite.ab.ca/accsmstr.htm
> =A0 =A0Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/


Sorry for taking so long to respond, I thought the thread was dead.

I have a form that opens hidden when anyone logs in. It's based on a
Users table and populates the record based on Currentuser() so that it
only shows that users record. It can see changes made to that record
by the administrator and react to them. In other words, if i want to
limit access to particular forms, I can lock them out based on that,
If i want to kick a particular user out, it also is based on that
table. So in that case, the answer is Yes, I do have a form open
based on a table on the BE which is always linked as long as someone
is logged in.

When editing however, I only have the form open that I'm currently
editing (I bypass the autoexec when editing) however that is generally
if not always based on a recordset from the BE.

Also, I do not relink tables based on code (sounds like it would be
what i need thought). I'm just using the linked table manager. It
seems to be working for me. I just accepted that I can only upload a
changed copy when i can have exclusive access to the BE data so i can
relink my Edited copy.


Thanks Much
Snoopy 33
Ben Casey

Re: DB Slows to a crawl when editing FE

Snoopy33 wrote:

>I have a form that opens hidden when anyone logs in. It's based on a
>Users table and populates the record based on Currentuser() so that it
>only shows that users record. It can see changes made to that record
>by the administrator and react to them. In other words, if i want to
>limit access to particular forms, I can lock them out based on that,
>If i want to kick a particular user out, it also is based on that
>table. So in that case, the answer is Yes, I do have a form open
>based on a table on the BE which is always linked as long as someone
>is logged in.
>
>When editing however, I only have the form open that I'm currently
>editing (I bypass the autoexec when editing) however that is generally
>if not always based on a recordset from the BE.

A lot of people do that. So open up a form, any bound form, such as that hidden one,
and leave it open while you are editing.

>Also, I do not relink tables based on code (sounds like it would be
>what i need thought). I'm just using the linked table manager. It
>seems to be working for me. I just accepted that I can only upload a
>changed copy when i can have exclusive access to the BE data so i can
>relink my Edited copy.

Relink Access tables from code
http://www.mvps.org/access/tables/tbl0009.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Re: DB Slows to a crawl when editing FE

"Tony Toews [MVP]" wrote in
news:jd6fp3tnqgb084me0g3evpo1qn9lp7adup@4ax.com:

> A lot of people do that. So open up a form, any bound form, such as
> that hidden one, and leave it open while you are editing.

Never did nothing for me, notimes.

Re: DB Slows to a crawl when editing FE

On Jan 23, 1:48=A0pm, "Tony Toews [MVP]" wrote:
> Snoopy33 wrote:
> >I have a form that opens hidden when anyone logs in. =A0It's based on a
> >Users table and populates the record based on Currentuser() so that it
> >only shows that users record. =A0It can see changes made to that record
> >by the administrator and react to them. =A0In other words, if i want to
> >limit access to particular forms, I can lock them out based on that,
> >If i want to kick a particular user out, it also is based on that
> >table. =A0So in that case, the answer is Yes, I do have a form open
> >based on a table on the BE which is always linked as long as someone
> >is logged in.
>
> >When editing however, I only have the form open that I'm currently
> >editing (I bypass the autoexec when editing) however that is generally
> >if not always based on a recordset from the BE.
>
> A lot of people do that. =A0So open up a form, any bound form, such as tha=
t hidden one,
> and leave it open while you are editing.
>
> >Also, I do not relink tables based on code (sounds like it would be
> >what i need thought). =A0I'm just using the linked table manager. =A0It
> >seems to be working for me. =A0I just accepted that I can only upload a
> >changed copy when i can have exclusive access to the BE data so i can
> >relink my Edited copy.
>
> Relink Access tables from codehttp://www.mvps.org/access/tables/tbl0009.ht=
m
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> =A0 =A0Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> =A0 =A0Microsoft Access Links, Hints, Tips & Accounting Systems athttp://w=
ww.granite.ab.ca/accsmstr.htm
> =A0 =A0Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/


IT WORKS!!!!!!!!!!!!!!!

Not sure why, but having a form open / minimized linked to data on BE
makes editing a breeze....


Thanks a Million!!!

Ben

Re: DB Slows to a crawl when editing FE

Snoopy33 wrote:

>IT WORKS!!!!!!!!!!!!!!!
>
>Not sure why, but having a form open / minimized linked to data on BE
>makes editing a breeze....

Same reason it helps with the users performance.

>Thanks a Million!!!

You're welcome.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Re: DB Slows to a crawl when editing FE

lyle fairfield wrote:

>> A lot of people do that. So open up a form, any bound form, such as
>> that hidden one, and leave it open while you are editing.
>
>Never did nothing for me, notimes.

You've stated that in the past once or twice as I recall. And I have no idea as to
why.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Re: DB Slows to a crawl when editing FE

"Tony Toews [MVP]" wrote in
news:gacgp3d1efu9gc8bbs7rcq9lfa2hp3oa4l@4ax.com:

> lyle fairfield wrote:
>
>>> A lot of people do that. So open up a form, any bound form, such as
>>> that hidden one, and leave it open while you are editing.
>>
>>Never did nothing for me, notimes.
>
> You've stated that in the past once or twice as I recall. And I have
> no idea as to why.
>
> Tony

Perhaps, I should have phrased my response in another way.

Form design for me has always been fast. When I [open up a form, any bound
form, such as a hidden one, and leave it open while I am editing] it is
still fast, but not faster. So I don't bother to do so.

Re: DB Slows to a crawl when editing FE

lyle fairfield wrote:

>>>> A lot of people do that. So open up a form, any bound form, such as
>>>> that hidden one, and leave it open while you are editing.
>>>
>>>Never did nothing for me, notimes.
>>
>> You've stated that in the past once or twice as I recall. And I have
>> no idea as to why.
>>
>> Tony
>
>Perhaps, I should have phrased my response in another way.
>
>Form design for me has always been fast. When I [open up a form, any bound
>form, such as a hidden one, and leave it open while I am editing] it is
>still fast, but not faster. So I don't bother to do so.

Oh, hold on a sec. Are you developing with the backend on your local system? If so
the performance hit of not keeping a form or link to the back end isn't much of a
problem. It's when you have a user already using an MDB on a server that your
performance really suffers without an always open bound form.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/