Good Afternoon Ted, Paul and Kevin: Thanks for the speedy reply! I checked the Anti Virus program and all was ok there. I didn't see where it was kicking on to do a scan while in a write. Nor could I find where to exclude file types for a virus check in the dynamic virus protection settings... The JPEGs on the user's notebook were hooked to MS Photo Editor. Mine are hooked to the photo fax viewer. So I made the change. I also went threw his startup registry and removed all the program loads that do not effect the machine operation. I launched the app and entered somewhere around 12 images and all behaved as expected. The user will continue loading the images later today so I am sure I will get some feedback. I hope this fixes the issue. As you all know it is very frustrating to have an issue on a user's box and not being to duplicate the same issue on the development box. Thanks for all your help. It is greatly appreciated. Best regards,
Jack Skelley ________________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ted Roche [EMAIL PROTECTED] Sent: Thursday, September 18, 2008 2:54 PM To: [EMAIL PROTECTED] Subject: Re: VFP6: General Field Write Is Slow... On Thu, Sep 18, 2008 at 2:30 PM, Jack Skelley <[EMAIL PROTECTED]> wrote: > Every once in a while the Append General from filename hangs for 10 minutes > or so and then the program continues ok. I have verified that the hang is on > the Append General construct. General Fields are funny beasts. They depend on the application that's assigned to the particular document type in order to store the document in a field. So, appending a Word document will invoke Word, an Excel document will invoke Excel. The maddening thing is that every clients machine might be configured differently. You'll want to determine what application your client has associated with JPEG files. The second thing General Fields do is have the associated application create a bitmap in uncompressed BMP format that's used as a representation of the contents of the general field when you're doing operations like browsing. You'll see a big blue "W" for a word document or the styled "XL" for an Excel doc, rather than a miniature screenshot of the document. But graphics tend to generate an exact image of the graphic, and it is sometimes HUGE, depending on the original source document. I've seen 20 megabyte BMPs, uncompressed, when storing a JPEG of a few hundred K. It may be the thrashing of generating the BMP and/or storing it that's causing the problem. General Fields were a cool idea back when OLE stood for Object Linking and Embedding. Now, it's probably a lot better to store the files name and location in the database and leave the actual OLE/COM object on disk, imo. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
