Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
 Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : ASP.NET vs Classic ASPSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v7 Forum

 New Topic 
 
 Post Reply 
[1]  
 ASP.NET vs Classic ASP 
 Author   Message 
  Mark 
  
 Group: Members 
 Posts: 2 
 Joined: 2006-12-13 
 Profile
 Posted : 2006-12-14 09:25:49

Quickbooks version:  Premier 2007 all updates as of Dec-13, 2006

QODBC version: 7.00.00.199 running in Web Server mode (testDCOM.asp = Success)

 

When I run the qbcust.asp, it finishes in about 2-3 seconds

When I run similiar code in ASP.NET, using the same SQL that returns the same results.  It takes 5+ seconds

 I am not using OPTIMIZATION (doing so in ASP.NET took 16+ minutes for 66 records, according to the Driver Status window)

 

Please verify that this time difference between ASP.NET and Classic ASP are typical.  I have been searching the support and FAQ's for any help in speeding up ASP.NET to no avail.

Thank You

Mark

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-12-14 09:31:31

Using QODBC on ASP.NET is slow when retrieving field values. "SELECT * FROM Vendor" took ASP.NET to retrieve 3 to 5 second avg per record or row. But switching to AspCompat="true" will yield 45 to 60 records per second. Retrieval using classic ASP is fine too.

ASPCompat is a configuration setting at the start of your code. For example:

<%@ Page AspCompat="true" Language="VB" %>

<script runat="server">
    ' The components is created at construction time.
    Dim comObj As MyComObject = New MyComObject()
   
    Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
        ' The object is first used here.
        comObj.DoSomething()
    End Sub
</script>

<html  >
<head runat="server">
    <title>Untitled Page</title>
</head>
<body>
    <form id="form1" runat="server">
    <div>
   
    </div>
    </form>
</body>
</html>

 

  Top 
  Mark 
  
 Group: Members 
 Posts: 2 
 Joined: 2006-12-13 
 Profile
 Posted : 2006-12-14 09:47:08

Much thanks! 

further info for others regarding ASPCompat="true"

 

If you're writing an ASP.net page that invokes a RCW (runtime callable wrapper) to a COM component... you may need to include the attribute 'ASPCompat=True' in your page directive.

In particular, if you have this situation:

"It worked fine in traditional ASP, but now it fails in ASP.net"

then it may be because ASP uses a STA (single-threaded-apartment) threading model, which the COM component may rely upon when returning calls.

The way to get the component to behave in ASP.net is to include that attribute, 'ASPCompat=True' in the calling page's page directive.

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-03-01 07:45:01
See also the msdn .NET Framework Developer Center:  http://msdn2.microsoft.com/en-us/library/system.stathreadattribute.aspx  

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to