Re: Stop() behaviour & Access Violation (General questions)

by wodSupport, Friday, January 06, 2006, 01:41 (6678 days ago) @ wodSupport

Ok, I made additional change, but only to protect myself against crash. You can request update.

Real problem still remains - you're holding one reference too many (perhaps not by your fault). In LoginPassword event, you must release User object, and that should fix the problem even with the version you already have.

Can you try that?

locked

3364 views

Complete thread:

Stop() behaviour & Access Violation - David Lucas, 2006-01-04, 16:16
- Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-04, 19:24
  - Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-04, 19:26
    - Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-04, 19:42
      - Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-06, 01:41

Many thanks for your excellent support service. I can see why you have a long list of excellent testimonials on your website.

Martyn Walker

Batmore Technolgies

...wodFtpDlx was exactly what I needed, it worked, and it was priced right...

David Keenan

Serengeti Systems Incorporated

Your customer service was excellent, and I will look at your products in the future for precisely that reason.

Charles Taylor

InterWeave, Inc.

...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...

Steven Jones

SABIEN project

Not only wodSFTPdll is excellent, the service you have provided is outstanding and second to none!

Ian D. Mead, author of UltraEdit-32

IDM Computer Solutions

You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.

David Keenan

Serengeti Systems Incorporated