Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Another Major Bug - COM+ Crash In DBC SP
Message
From
23/12/2004 11:48:26
 
 
To
23/12/2004 06:23:30
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00971709
Message ID:
00971828
Views:
24
Hi Jeff,

>The memo file was and is not corrupt.

And what makes you think that? The fact that VFP8 doesn't complain? This is not a good test for MEMO file integrity.

> The error occurs only if the table is opened exclusive.

So? VFP uses MEMO files a little bit differently when it is shared, might as well avoid accessing the corrupted spot.

Have you tried to recreate the MEMO file the way I've suggested?
If you have and the problem is still there or if you decided to do nothing and wait for SP1, which won't fix the problem if the file is corrupted, then you can zip the .DBF and .FPT files up (assuming the size is reasonable) and send them to my e-mail.

Thanks,
Aleksey.




>The memo file was and is not corrupt. The error occurrs only if the table is opened exclusive. If opened shared, no error. No buffering. No other users were accessing the COM server when I tested this.
>
>In my book, when a COM Server crashes, it is a crash.
>
>Thanks
>
>>Hi Jeff,
>>
>>Have you considered a possibility that the MEMO file is indeed corrupted? VFP9 is more sensitive to a MEMO file corruption. It detects corruption that prior versions do not. You should be able to recover content that can be accessed by VFP8. One way to do this is to open the table in VFP8, COPY TO ... then rename (don't forget to backup original files before).
>>
>>BTW, an error is not a crash. Please call things what they are.
>>
>>Thanks,
>>Aleksey.
>>
>>>Geeeeeeeez..... and this is supposed to be a stable release?
>>>
>>>Getting COM Server crashes with bogus "Memo file is missing or is invalid" error messages during a REPLACE in a VFP9 DBC Stored Proc.
>>>
>>>This stuff has been working flawlessly in VFP8 for months. There are other problems I don't have time to write about.
>>>
>>>What really makes me mad about all of this is that there are new features in VFP9 that we really need. But all this other garbage prevents us from using VFP9 until a service pack is released which may or may not address the issues I have found in JUST A FEW HOURS!!!
>>>
>>>I feel like asking for our money back. MERRY XMAS
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform