Hi everyone. Thanks to everyone for their suggestions which I stayed up late last night and went through one by one. Finally went to bed about 12.00 pm. Woke up this morning and for some reason thought I would look at another problem. (Just maybe the other problem would go away). Anyway to cut a long story short, I decided to look at an error which was being thrown up from my error handler routine. When an error occurs it throws up a dialogue to enter how and when it happened to then be emailed back to my office. (I will be putting up my experiences with this on my ARG blog next week). Immediately I got an error Cannot find "GetWindRec.prg". Investigating with code references I found one reference to Commctrl.vcx and three references in my main.prg. I used a windows GetWindRect function there to find the height of the task bar. I first of all commented out that code without result. I then removed the CommCtr.vcx form my project. Of course on a rebuild it came back so I looked to see what it was being used for and found it was the VCX used for the Status bar. This was provided by Arg Software instead of the standard one. I removed the status bar and the VCX also any references in code, and built the application. On test the error routine worked correctly. On the off chance I copied the executable to my client and ran it there. Eureka problem solved. Oh dear. Comments from Client, "Where's the status bar gone we really liked that. "Here we go again."
Cheers Peter Peter Hart Computers Link to Error handler routine which I have modified (It is brilliant, Have made it also available from Ribbon to use to report suggestions) http://www.sweetpotatosoftware.com/SPSBlog/2008/11/24/ProfessionalErrorH andlingForVFPApplications.aspx Dave Crozier Sent: 19 August 2009 15:46 Subject: RE: Buffer Overrun. Peter, Just a wild stab here but have you tried at the beginning of your prog (in the loader?) : _VFP.Autoyield=.F. "Specifies whether an instance of Visual FoxPro processes pending Windows events between execution of each line of user program code." I know this was specifically designed to work with activex objects but I have found that it is necessary with other supposedly "well behaved". It is scoped VFP wide not per datasession. Malcolm Greene Sent: 19 August 2009 15:01 Subject: RE: Buffer Overrun. Some ideas off the top of my head: 1. Make sure you don't have a corrupted foxuser.dbf. If you can avoid using a foxuser resource file, do it (turn it off in your config.fpw) 2. Open a shell prompt, and simplify your path to the min length possible. Then run your app. 3. Use SET COVERAGE to keep a coverage log (works at runtime with VFP 9) - see if you can determine where a crash happens by looking at your coverage log ouptut. 4. The bb* utilities may use an FLL that may be causing compatibility problems. How many FLL files are you using? Tracy Pearson Sent: 19 August 2009 14:31 Search the clients computer for the VFP9*.DLL files. I'd use the command window "DIR C:\VFP9*.DLL /S/B" The S for subdirectories, the B for blank meaning just the full path of the files found. You might be using SP 1 runtime with SP 2 EXE, or both. I've also seen a bad environment PATH cause a problem. Original post by Peter Hart Updated my clients machine after making one change to the application. Now he gets a "Buffer overrun detected" Error with MS Visual C++ in the message title. Anyone had this error and knows why. Googled and updated client to VFP SP2 run times. Did windows updates. No good. Changed back to previous backup of application and still same error. _______________________________________________ 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/a57fa4cf19531343a2ee11b57db8e3af04c...@server.peterhartcomputers.local ** 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.
