• Keeping the connection open and shared across all SalesOrderLine INSERTS
• Adding AspCompat="true" to the ASP.NET aspx page that calls the web service
• [STAThreadAttribute] added to each web method in the Web Service

For large batches you can also try SP_BATCH, see: Are there any special stored procedures that can assist me in programming? 

ASP.NET runs queries as multiple treads, and the QODBC optimizer is single user only. So you need to setup a different optimizer file for the ASP.NET application to use than the other disktop applications. To do this, set up a seperate System DSN (see: How do I create or configure a QODBC DSN? ) and specify a fixed location of the optimizer database folder for the ASP.NET application to use (like: C:\Program Files\QODBC Driver for QuickBooks) instead of the default %UserProfile% method. Finally the user or system account used (Anonymous web user IUSR_machinename, ASPNET user and INTERACTIVE) by the ASP.NET application must all have full rights to the optimizer folder.

You don't need to optimize all the QODBC tables if you're just using a handful of tables. Simply rebuild (sp_optimizefullsync) or update (sp_optimizeupdatesync) the tables you use from within your ASP.NET application using:

sp_optimizefullsync InvoiceLine

sp_optimizeupdatesync InvoiceLine

See: How do I setup the QODBC Optimizer? Where are the Optimizer options?  for more on how the optimize works.

The stored procedure:

sp_optimizeupdatesync SalesOrderLine

returns null (no rows), so that's most likely the problem. Once the tables have been optimized you don't need to run sp_optimizeupdatesync SalesOrderLine as this is done automatically by QODBC. If you need to rebuild a optimized table simply use the VERIFY tag like this:

SELECT "Name","LastName","FirstName","BillAddressAddr1",
"BillAddressAddr2","BillAddressCity",
"BillAddressState","BillAddressPostalcode"
from Customer VERIFY

We are trying to set up and ASP.NET program that reads customer data from Quickbooks using QODBC.    The platform is WIndows Server 2003.  We have the Use DCOM servers checked and setup all the authorizations.  We are using ADODB, but on opening the connection it hangs and eventually gives a timeout error.  I have read through all I could find, but cannot get passed this problem.  Please help.

Thanks

Stephan

It simply gives a "HTTP Error 404 - File or directory not found. Internet Information Services (IIS)" I think it is because this is an .ASP file and not .ASPX.  We have two asp.net projects running on this server and they work fine.  I tried to put this file on .net platform 2.0 and also in 1.1, but both gave this error.

[STAThread]
        internal static string ExecuteNonQuery(string query, string table, DataConnection qbConnection)
        {
            log4net.Config.XmlConfigurator.Configure();

            ILog log = LogManager.GetLogger(typeof(DataAccess));

            if (log.IsDebugEnabled)
                log.Debug("Running query '" + query + "'");

            OdbcConnection connection = qbConnection.ActiveConnection;

            string returnId = null;
           
            try
            {
                OdbcCommand command = new OdbcCommand();
                command.CommandText = query;
                command.Connection = connection;
                command.CommandType = System.Data.CommandType.Text;

                command.ExecuteNonQuery();

                command.CommandText = "sp_lastinsertid " + table;

                OdbcDataReader reader = command.ExecuteReader();


                try
                {
                    if (reader.Read())
                    {
                        returnId = reader[0].ToString();
                    }
                }
                finally
                {
                    if (reader != null)
                    {
                        reader.Close();
                        reader.Dispose();
                        reader = null;
                    }


                }
            }
            catch (Exception ex)
            {
                log.Fatal(ex.Message + "(" + ex.Source + ")" );
                throw ex;
            }
            finally
            {
            }

            return returnId;


       }