Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / July 2005

Tip: Looking for answers? Try searching our database.

Slow performance on newly split database

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Trauton - 22 Jul 2005 07:58 GMT
Hi,
I just split a brand new database and the forms are taking 30 seconds or
more to open, whereas while the application was in my computer they would
open almost immediately.  It is a small application (under 30MB); all users
will be connecting to it from different locations in the US using a FE mde
file that contains all the objects except for the tables which are located in
the BE mdb file in a network server.  The forms filter the records so the
users only see the ones that are tagged to them.  I have created a persistent
connection, Track Name AutoCorrect is off, converted the FE file to mde.  The
only thing I haven't done yet is to shorten the name of the BE file.

I woud really appreciate any suggestions to improve the performance.

Trauton
Trauton - 22 Jul 2005 17:45 GMT
As a follow up question to my initial post, Would converting the forms to
Pages for web access solve the delay issue?  If so, would a split database
still be needed? Would you then be having the switchboard open the Pages
instead of the Forms?

Thanks!

Trauton

> Hi,
> I just split a brand new database and the forms are taking 30 seconds or
[quoted text clipped - 10 lines]
>
> Trauton
Tony Toews - 22 Jul 2005 19:10 GMT
>I just split a brand new database and the forms are taking 30 seconds or
>more to open, whereas while the application was in my computer they would
[quoted text clipped - 5 lines]
>connection, Track Name AutoCorrect is off, converted the FE file to mde.  The
>only thing I haven't done yet is to shorten the name of the BE file.

Users all over the country?   On your local LAN performance will be
fine.   On a WAN performance will suck.

Your options are
1) as you pointed out in another posting use a web app of some sort.
2) use Terminal Server/Citrix
3) convert the backend to SQL Server.

Tony
Signature

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

Trauton - 22 Jul 2005 19:22 GMT
Thanks a lot Tony.  It seems that using Terminal Server may be a good
solution which doesn't involve converting the Access application (trying to
save time).  Will it provide a reasonable response time?  What does it
involve?

-Trauton

> >I just split a brand new database and the forms are taking 30 seconds or
> >more to open, whereas while the application was in my computer they would
[quoted text clipped - 15 lines]
>
> Tony
Tony Toews - 23 Jul 2005 04:07 GMT
>Thanks a lot Tony.  It seems that using Terminal Server may be a good
>solution which doesn't involve converting the Access application (trying to
>save time).  Will it provide a reasonable response time?  What does it
>involve?

It's somewhat expensive when it comes to TS licenses and such.   You
should discuss this with your IT department.  OTOH the licenses can be
cheaper than a rewrite.

TS is essentially multiple users sharing a single computer.  The
screen drawing commands are sent to the client system.  The mouse
movements, clicks and keyboard entries are sent back to the server.

It works reasonably well even on a dial up in a motel room.  Although
I wouldn't recommend that for heavy duty data entry.   A client has
been happily running TS over cell phone connections from remote job
sites where land line service is many miles away.

See
http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx
for more information than you could possibly want.

Tony
Signature

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

Trauton - 23 Jul 2005 05:56 GMT
I appreciate your help Tony.  Certainly helps put things in perspective.

Trauton

> >Thanks a lot Tony.  It seems that using Terminal Server may be a good
> >solution which doesn't involve converting the Access application (trying to
[quoted text clipped - 19 lines]
>
> Tony
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.