Calculating in status bar, occasional 45 second delay on runtime machines



I am trying to set up a custom made Access front-end, SQL back-end
(utilizing Linked Tables via the upsize wizard) Purchasing Database
for my company. I am running into some problems.

Access 2003 Front End - ME
Access 2003 Runtime - Clients
SQL Server 2000 - Server Backend (located on a Microsoft Small
Business Server 2003 machine)


I install Access Runtime on a client's machine, then have them try
using the front-end. When it comes to switching to different records
using the comboboxes, it will switch them very quickly several times,
and then it will freeze with "Calculating" showing in the status bar.
It will remain in this state for about 45 seconds before finally
switching to the new record. Then I can switch quickly through several
more records very fast until (seemingly randomly) it will stop on
another transition for about 45 seconds...and then finally continue
working just fine until the next stop...


It has six linked tables, some with several hundred records in them,
others with only sample data. All these tables are located on the
backend SQL server. The switchboard table remains on the front-end.

To make it easier for our Purchasers I have included comboboxes that
list all Suppliers, or on another form a combobox that lists all known
Purchase orders etc. (Although I realize this is not best practices, I
figured down the line if they got too big I could limit the number of
records returned) On one form and one report there is one dlookup,
though they are not related to my problem. (Since I have removed the
dlookup and had same problem)

I have included a connection string on the switchboard form's on load
event:

Set conn = CreateObject("ADODB.Connection")
strConnString = "Provider=MSDASQL; Driver={SQL Server};
Server=servername\sqlserver; Database=Purchasing; PageTimeout=5000;
Trusted_Connection=yes;Uid=;Pwd=;"
conn.Open strConnString
(though the above connection string seems to have little positive
effect on the problem)

I have also included a simple form to load and try to keep the
connection open while the user deals with other forms, again with no
results.

I believe I have set the permissions correctly on the SQL server back-
end...

It runs fine on my own computer, with no delays. (Perhaps because I
have a full Access edition instead of run-time?) Running it on other
clients with the runtimes always hits this problem, regardless of how
powerful their computers are.

It just strikes me as strange how the access front-end can work so
instantaneously for a few records and then hit a 45 second rut, and
then work instantaneously again. It it was a consistant delay I could
perhaps understand...but not this.

I am hoping that someone else out there has run into this problem
before and comes up with a solution, I've spent quite a bit of time
tweaking this and not gotten anywhere. : )

.



Relevant Pages

  • Locked records
    ... The data is held on a SQL 2000 server with Access front-end. ... If I click on I then get another error message: ... on the form and that I have not VBA updating any fields upon opening. ...
    (microsoft.public.access.formscoding)
  • Re: Still Having a Problem Counting a String Field
    ... Switching to an outer ... In the SQL code it is ... >listed as an INNER JOIN twice, so should I switch the JOIN type to an OUTER ... >>> is the Crystal Syntax. ...
    (microsoft.public.vb.crystal)
  • Re: Possibly stupid question for you IBM mainframers... :-)
    ... The differences between ways of handling DB2 code within CoBOL ... > programs can be bigger than switching between Oracle and DB2. ... While SQL is SQL is SQL, ... what you know about writing performant Queries in DBMS 1 if you switch to ...
    (comp.lang.cobol)
  • good, thorough documentation on full text issues?
    ... out website is starting to get serious about switching from SQL 2000 to SQL ... fulltext searching. ... catalogs than the underlying base tables. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Export SQL statement from query to text file
    ... > What's wrong with the good old copy/paste routine? ... > Switching to SQL view automatically selects the block of text. ... >> W Dean ...
    (microsoft.public.access.queries)