GenoPro Support Forum

Hope this helps.

Buck 

Buck

Scio me nihil scire 

Scio me nihil scire 

...Or try recreating the bug in a new file... but I think it won't happen in a new file.

Only solution is to believe in Dan, and ask him to delete it afterwards!

---

"εν οιδα οτι ουδεν οιδα" (Σωκρατησ)  - "The only thing that I know is that I don't know anything" (Socrates)

After fixing the bug VBScript Runtime Error in Report Generator, I will wait for Buck to confirm if the fix also fixed this crashing bug.

The best solution is to send a small sample .gno file producing the bug.  Most people do send their whole .gno file because it is faster and safer than isolating the problem.  This is fine too because I have debugging tools for this task and it is usually very quick for me to find where the problem is.

I understand a .gno file contains sensitive information.  I used to be the IT manager of a large accounting firm and had access to all files of all employees, which included accounting information of their customers.  I was manipulating files containing a lot of sensitive information, which included SSNs, SINs, TINs, banking information, contact information and business secrets.  I know the importance of confidential information.  When I receive a .gno file, I treat this information strictly on a professional basis.  I find the bug, fix it, and move the file into a special archive folder in case the problem re-appear later.  If the file is very large, I usually run it through the report generator to see if there are no "internal warnings" or memory leaks in my code.  On my machine, the file GenoPro.exe is 4.5 MB containing extra code to check data integrity.  The generated report is immediately deleted because I don't need those HTML files.  By the way, this is how GenoPro generated over one million HTML pages on my machine.

If the customer requested his/her to be deleted, I delete it as soon as the fix is confirmed, which is usually on the same day.  I have no interest in the family secrets of my customers.  I am working hard make a quality product and want to make sure GenoPro has a good reputation.  It is bad for business to have bad press, and this is why I am extremely vigilant on this issue.  In the past, some individuals have posted their .gno file on this forum instead of sending it by email.  As soon as I downloaded their .gno file and fixed the bug, I deleted the attachments to protect their data.

By the way, file size is not an issue.  I have received once an attachment of 70 MB!  You may do a file "Save As" to reduce by half the .gno file size before sending it by email.

Edited: Friday, September 23, 2005 by GenoProSupport