- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On one of four computers running DVF 6.6, attempting to OPEN with new subroutine causes DVF to crash. Other computers which SEEM to have the same code, do not fail. Also, if the new code is added to an existing subroutine, the problem does not occur. I've been wrestling with this for about 6 months by adding new code into existing working unrelated subroutine but I would dearly love to fix have a more elegant solution to this problem. Any help would be much appreciated.
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It would really help if (a) you could attach the code which fails and (b) tell us what the exact error message is - "crash" is not very descriptive or helpful.
As I understand it you have added a new subroutine to a project and that subroutine has an OPEN statement for a file, and this fails at run time. Is that correct?
Les
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The "crash" report started as follows:
" Microsoft Developer Studio has encountered a problem and needs to close. We are sorry for the inconvenience.. For more information about this error, click here" The CLOSE button also appears. Using the CLOSE button closes the Developer Studio, effectively kicking me out of Developer Studio which I described as crashing. When I do the "click here", I get information about DEVSHL.DLL and don't know what to do next. Actually I just should bave indicated a NEW file rather than using the OPEN and proceeded from there. I no longer remember why I was trying to use the OPEN button in this situation..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is one of those horrible situations to which there does not appear to be a simple answer. I have seen this happen on my pc a few times, and not always at the same point, during a rebuild of our software, some of my colleagues have never seen it.
All I can say is that when it has happened to me I restart VS, rebuild and it usually works ok - until the next time.
Sorry I can't help more.
Les
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page