Ted: Yep, those be them. I checked the event logs and there is nothing
there related to the problem. I'm inclined to agree with you because a
.CDX is left in the temp file after the program shuts down. It has zero
bytes.
Thanks,
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 06/22/2013 05:31 AM, Ted Roche wrote:
Okay, so you're refering to the threads:
http://leafe.com/archives/full_thread/480540
http://leafe.com/archives/full_thread/480828
http://leafe.com/archives/full_thread/480856
Which likely have nothing to do with the problem ;) Buffer overflow is one
of the fundamental errors that gets reported when nothing else traps it
first.
If nothing else has changed on the application, you've recompiled (and
PACKed?) the code and projects, and there's nothing especially different
about this machine (like they're running Windows 9), I'd be inclined to
blame the data. Does this workstation have its own stand-alone data or is
it sharing data with other workstations on a network? If the former. check
the data files, validate and pack. If the latter, and it works fine on
other workstations, well, never mind.
On Sat, Jun 22, 2013 at 8:19 AM, Jeff Johnson <[email protected]> wrote:
Ted: In the heat of battle I couldn't find the event logs. I will check
them today. The earlier posting mentioned visual c++ in the buffer overrun
and it happened when I closed my applications command window. When the
command window closed and the background jpg wanted to paint on the _screen
I got the buffer overrun. A CLEAR MEMORY in the destroy of my command
window form fixed the problem.
This one is happening after the user logs in and the application is
starting.
Thanks,
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 06/22/2013 04:21 AM, Ted Roche wrote:
Jeff:
I don't recall the earlier posting. What's the exact error message? Is
there anything in the system error logs?
______________________________**_________________
Post Messages to: [email protected]
Subscription Maintenance:
http://mail.leafe.com/mailman/**listinfo/profox<http://mail.leafe.com/mailman/listinfo/profox>
OT-free version of this list: http://mail.leafe.com/mailman/**
listinfo/profoxtech <http://mail.leafe.com/mailman/listinfo/profoxtech>
Searchable Archive:
http://leafe.com/archives/**search/profox<http://leafe.com/archives/search/profox>
This message: http://leafe.com/archives/**byMID/profox/51C59649.6020301@**
san-dc.com<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.
Report [OT] Abuse: http://leafe.com/reportAbuse/**
[email protected]<http://leafe.com/reportAbuse/[email protected]>
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.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.