ericp@beach.csulb.edu (Eric Pederson CSE) (02/22/91)
I have been running into a problem lately with open errors coming from a Clipper application. The error code that is returned is (0), which, according to Nantucket may happen on index files if the index is somehow corrupted, but should never happen on DBF files. Well, it's happening a lot on DBF files. Has anyone seen this problem before? It started cropping up after I made a lot of changes to the program. I have a few theories of what might be causing the problem: - The program size is getting very large. Could this be a symptom of ram cram? I am using Blinker (dynamic overlay linker) to link. - I am sometimes USEing a file that may already be open under a different alias (from a hot-key UDF). This seems to work ok but I am wondering if it is causing side this open error (0) as a side effect. Note that the error is occuring on files that *aren't* being opened twice. - I am now using the FUNCKY library for a few functions, namely the savegets()/restgets() combo. Has anyone had problems using these functions? - I am running VM/386 which has caused problems in the past, but this problem cropped up a couple months after the latest release of VM/386 was installed. I would appreciate any hints or ideas.. Eric Pederson - CSULB ericp@beach.csulb.edu
patterson@x102a.harris-atd.com (patterson stuart 00476) (02/25/91)
New versions of DOS autoload Share.exe, thus could be the problem. I have had the same error when opening to databases in different areas when share was running and the apps not written for multi-user. Hope this helps! Stuart