Advertisement

08.20.2008 at 02:25AM PDT, ID: 23662414
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.2

Speed Issues when converting Access 97 to Access 2003

Asked by Programmers in Microsoft Access Database, Access Coding/Macros

Tags:

I'm wondering why when I converted a Access 97 database with code to Access 2003, the code within it runs a lot slowly. For example the code below queries data from a sqlserver 2005 database and inserts into an Access table via recordsets. In Access 97, this runs quite smothly and takes 1-2 secs for each call but now in Access 2003 it takes between 40-60 secs.

Why the big difference? what can I do to minimise the speed differences. I am trying to aviod re writing the whole thing. The whole database modules is legacy code with the author no longer with the company.

Is there any steps I can take to make a difference.
Thanks for any help given. - BrianStart Free Trial 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:

Function db_sql_requests(merchant_id As Long) As Boolean
   Dim i As Integer
   Dim wsp As Workspace, dbs As Database, rs2 As Recordset
   Dim con As ADODB.Connection
   Dim cmd As ADODB.Command
   Dim rs As ADODB.Recordset
 
   'on error goto error handler
   On Error GoTo err_db_sql_requests
   db_sql_requests = False
 
   'return reference to current database and workspace
   Set dbs = CurrentDb
   Set wsp = DBEngine.Workspaces(0)
   Set rs2 = dbs.OpenRecordset("requests", dbOpenTable)
 
   'create and open a new connection to the sql WorldsmartMaster database
   Set con = New ADODB.Connection
   con.Open odbc_adoprovider
   
   'create a command object and a parameter object
   Set cmd = New ADODB.Command
   cmd.ActiveConnection = con
   cmd.CommandTimeout = 0
   cmd.CommandType = adCmdStoredProc
   cmd.CommandText = "spxRequests"
   cmd.Parameters.append cmd.CreateParameter("@iMerchantId", adInteger, adParamInput, 0, merchant_id)
 
   'create and open an updateable recordset (passing in the command object)
   Set rs = New ADODB.Recordset
   rs.CursorLocation = adUseClient
   rs.Open cmd, , adOpenStatic, adLockBatchOptimistic
   
   'if requests found
   If Not rs.EOF Then
 
      'append records
      Do While Not rs.EOF
         rs2.AddNew
         For i = 0 To rs.Fields.count - 1
            rs2.Fields(i) = rs.Fields(i)
         Next i
         rs2.update
         rs.MoveNext
      Loop
      
   End If
   
   'return true on function exit
   db_sql_hotcard_requests = True
 
'common exit call
exit_db_sql_requests:
   
   'close on exit or error
   rs.Close
   rs2.Close
   Set dbs = Nothing
   
   Exit Function
   
'common error call
err_db_sql_requests:
   process_error "db_sql_requests"
End Function
[+][-]08.20.2008 at 03:32AM PDT, ID: 22267868

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Microsoft Access Database, Access Coding/Macros
Tags: Microsoft Access VBA
Sign Up Now!
Solution Provided By: cactus_data
Participating Experts: 1
Solution Grade: A
 
 
[+][-]08.20.2008 at 06:07PM PDT, ID: 22275390

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08.20.2008 at 11:41PM PDT, ID: 22276778

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
 
Loading Advertisement...
20081112-EE-VQP-42 / EE_QW_2_20070628