>FYI: from my experience speed is VERY dependant on network, local queries on machine with QuickBooks installed have a reasonable performance, when accessed across network performance deteriorates significantly (another reason for a server based approach?)

Your code example is what I'm doing on a core i7 XP box when directly using the QB SDK. I doubt that my performance issue has to do with the network, or the box I'm using. Retrieving data from a Postgres database is in the mili-second range and retrieving data from QB is in seconds. And the Postgres DB in on the network and QB is on the same box as the app accessing it (maybe that's the real issue - on the same box).

Also testing reveals that most of the time spent is in two methods - the connection and begin session. At this time I'm just pre-loading the connection and begin session methods during the splash screen. The problem with pre-loading is I'm using a user license for each connection. I was hoping to avoid using the licenses. I think this has something to do with the way QB's database works and nothing else. I also note that QB should be running/started - otherwise it really takes a loooong time to start the process.

Johnf