inetroncce

Does anyone else experience the issues when shipping a sales order from (D-Tools to Quickbooks)of a 9-11 minute "handshake" period? The computer our designer is using pegs 100% of system resources and stalls out for this period every time we ship a sales order over. The computer is a P4 2.6Ghz pentium with 1 gig of RAM so it should not be processing power.

This is an incredible waste of resources so we are looking for any suggestions that might help speed up the process. If everyone using quicklinks is experiencing the same issue, it may be a software bug, but that is hard to believe.

Please help!!!

Ron Pitcock, Jr.
Colorado Custom Electronics
(303) 399-0304

JordanC

If everything is going through okay and just takes too long, then it's going to be a networking or computer speed issue. As a test, I sent the same project to QB using sales order & estimate with two different computers, one old and one new with the same network set up. I noticed that the older computer was much slower. DT's & QB are rather large programs and really tax the computer. What to do, beef up the RAM & CPU, make sure no other programs are running during the transfer other than QB & Dt's and that your the only user in QB. I am assuming uour doing this over a network and that QB & DT's is running on another server, so you want to make sure that the network speed is up to par.

__________________

Space available for rent.

wirebro

We have been fighting with d-tools about an admitted SQL server bug that comes up when we try to generate a sales order, generally a 90 second or so stall. They have thus far adpoted a 'shut-up and wait for the new release' policy in response. The transfer process is exceedingly slow for us as well but I'm not sure if this is the same issue you are having. Yesterday I spent about 6 hours trying to resolve a transfer problem, mostly due to the d-tools response time.

I'm still in the process of crafting an email to the president regarding this issue. A couple more wasted days I should have the proper steam built up.

BlakeV

First, you cannot win a "Fight" with D-tools because we have no intention of "fighting back".
Second, we have never told anyone to "shut up and wait". In fact it is not our policy to tell anyone to shut up.
Thirdly, our president has already graciously responded to your email from a few weeks ago.
I also believe our chief developer also spoke with you personally as well.
So, Dustin has helped you out from tech support, our chief of development Rick Wolf has helped you out from development and our president Adam Stone has also responded to your inquiry.

Like i said, we are always willing to help, even you, as we already have and hope to continue to do in a profesional, productive and "friendly" manner.

__________________
Blake
D-Jedi Master

jims

This may be an entirely different subject.. .but we have found that the first thing QL does is look for the next available number from the QB file. So if it is a PO you are creating, QL must first find the next available number in QB. Starting with 1, then 2, etc... If the next available number is 2882, then it will take a long time to get to it.
Perhaps what is needed it some form of input from users on the Set up tab. Where users can dictate where QL will start looking for numbers... ie Start PO count at 2881. The input could be updated from time to time, when the slowness becomes an issue.

PsiKoTicK

It can be something very simple: Is Norton installed? If you run Norton, it is very likely hindering your traffic flow. Get rid of it entirely, and use an AntiVirus that doesn't put it's fingers everywhere (I recommend AVG generally). The current Norton AntiVirus 2006 (even without the Internet Security part) blocks "worm like activity" and acts as a partial firewall, which can SIGNIFICANTLY slow down network traffic.

It can also be a network issue - if you are using a Windows Server, and Windows 2000 Pro, the system (unless setup exactly right) has to re-authenticate EVERY TIME it tries to connect... XP authenticates and stays authenticated unless the connection is dropped.

If you are just running Windows XP as your "server" then this shouldn't be an issue, but you may have bad wiring, or a power line next to your data line causing interference. "But everything else works fine!" isn't always a valid response, either, because on small things, the interference is minimal... on a large file, each and every packet has to be responded to, and the mistakes caused by interference can add up, and can add up VERY quickly to a ridiculous wait.

There may be other issues, but I'd try these first.

jims

That's all good information, but it's slow when we open it on the server too. We tried putting d-tools and qb on the same xp machine. There was no significant improvement.

Reed Phillips

LinkTools perfomance has been significantly improved in V5. The slow startup issue has been corrected.

-reed

__________________
Reed Phillips