Too much in front end?

[dalmond]

What started out as a simple dispatching log has now turned into a
complete Security Department Databse...sorta . I thank many many people
who shared their knowledge to help me accomplish what I've done.

Everything that is generated in our department, service calls,
reports, property inventory, etc is based off of a number generated
from the dispatch database. Because of that, I have been able to
incorporate different tasks, all in the same FE/BE setup but the FE has
become increasingly slow and I am worried that I will see a problem
with data being corrupted or really anything negative. My FE is about
4mbs and is copied from the server location at each login. This is to
distribute the FE after any changes/updates.

My question is this, would I be better off having multiple FE for each
seperate task? EG Dispatch logs, property logs, incident reports,
officer records, etc.?

Thanks again for your past and future help

Dave

[dalmond]

That's comforting. I've read that saved queries are faster than coded
queries so I've attempted to go that route as much as possible. I've
also gleened most MVP sites and posts for efficacy tips and techniques.
Thanks all for your attention to this.

Dave
w_a_n_n_a_l_l_-@-_s_b_c_g_l_o_b_ a_l._n_e_t wrote:

Status on our current Access 2003 MDE app:

329 Forms
47 Modules (about one third of them of them class modules)
891 Queries
80 Reports
64 Tables (local)
188 Tables (SQL Server)
About 60 K lines of VBA code

In production we see acceptable performance and rarely experience any
problem not caused by some oversight of yours truly.

I don't see why 14 forms et al would be the cause of any great problems.

[Larry Linson]

<da*****@verizo n.net> wrote

That's comforting. I've read that saved
queries are faster than coded queries so
I've attempted to go that route as much
as possible. I've also gleened most MVP
sites and posts for efficacy tips and techniques.
Thanks all for your attention to this.

I've read and heard that same advice, but to be honest, I have never seen a
case where you could determine the difference between the two at the user's
workstation. CAVEAT: I have not tried this comparison with massive amounts
of data.

Larry Linson
Microsoft Access MVP

[David W. Fenton]

w_a_n_n_a_l_l_ -@-_s_b_c_g_l_o_b_ a_l._n_e_t wrote in
news:9l******** ***********@new ssvr12.news.pro digy.com:

Not sure where you got that idea. One only. Actually, one on the
Texas server and one on the Florida server, so users in each
office are not pulling the app itself from further than down the
hall.

Then you're DOING IT WRONG. Sharing a front end is just stupid.
Period.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

da*****@verizon .net wrote in
news:11******** **************@ f6g2000cwb.goog legroups.com:

I've read that saved queries are faster than coded
queries so I've attempted to go that route as much as possible.

The difference is going to be completely negligible in the vast
number of situations. What you get with a saved query is a
precompiled query plan that is optimized by Jet to be as efficient
as possible. If you don't have a saved query the optimization is
done each time you run the SQL.

I used to litter my apps with lots of saved queries for precisely
the reason you give, but managing them became too hard, and now I
save a query only when it has an advantage other than supposed
performance increases.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[(PeteCresswell)]

Per da*****@verizon .net:

Slow to me is relative to how it responded when the databas

This probably isn't going to help, but is worth doing as SOP anyhow: Open up
each table in Design mode, right click anywhere, select 'Properties', and change
'SubDatasheet Name' from '[Auto]' to '[None]' - unless, of course you are
using that feature.

I've seen it speed up the opening of some tables significantly.
--
PeteCresswell

[w_a_n_n_a_l_l_ -]

Now we're rehashing old topics. You indicated previously that you have had
great problems with this. I have not.

I was correcting your mistake in thinking that I said I was keeping a copy
of the front end on the network file server for each user, nothing more.

[Arno R]

"(PeteCresswell )" <[e-mail]> schreef in bericht news:6h******** *************** *********@4ax.c om...

Per da*****@verizon .net:

Slow to me is relative to how it responded when the databas

This probably isn't going to help, but is worth doing as SOP anyhow: Open up
each table in Design mode, right click anywhere, select 'Properties', and change
'SubDatasheet Name' from '[Auto]' to '[None]' - unless, of course you are
using that feature.

I've seen it speed up the opening of some tables significantly.
--
PeteCresswell

Good idea, but I would not do this manually for each table ...
Look here: http://support.microsoft.com/?kbid=261000
There is code to TurnOffSubDataS heets() on that page.

Arno R

[David W. Fenton]

w_a_n_n_a_l_l_ -@-_s_b_c_g_l_o_b_ a_l._n_e_t wrote in
news:xz******** ************@ne wssvr29.news.pr odigy.net:

Now we're rehashing old topics. You indicated previously that you
have had great problems with this. I have not.
Well, perhaps some of the problems you are having would go away if
you'd distribute your apps properly.
I was correcting your mistake in thinking that I said I was
keeping a copy of the front end on the network file server for
each user, nothing more.

I knew perfectly well that you were doing it wrong when I asked the
question. I was trying to remind you of your error.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[w_a_n_n_a_l_l_ -]

I am not reporting any problems at this time. Could you have me confused
with another poster?

[David W. Fenton]

w_a_n_n_a_l_l_ -@-_s_b_c_g_l_o_b_ a_l._n_e_t wrote in
news:e8******** *************@n ewssvr29.news.p rodigy.net:

I am not reporting any problems at this time. Could you have me
confused with another poster?

Were you not commenting on the problem with the front end being
slow? Perhaps that's because it's being shared, which means it has
to be loaded across the network and that there is contention for the
objects being loaded by multiple users simultaneously.

And if you're sharing front ends, you *do* have a problem, whether
you choose to recognize it or not.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/