Data corruption of FoxPro source code files
Apr 3, 2019 7:14:04 GMT 1
Post by Jorge Zaldívar on Apr 3, 2019 7:14:04 GMT 1
Although my FoxPro programs run without any problems under vDos, for developing I have to use a real Windows XP computer (an old, keyboardless and screenless print server I connect to using TeamViewer) because, if I use vDos to edit screen (SCX+SCT) or menu (MNX+MNT) files, they get corrupted: when I try to save my changes, I will eventually get an error (File Read Error) and further attemps to access the snippets of code (to copy and save them) result in a File Not Open error.
Screen and menu (as well as project and report) source files are just tables ("databases") with different extensions, I guess the error is due to corruption of the memo file (in one case, the memo file was completely missing! - I was able to recover a previous version from Dropbox history).
Why doesn't this happen with the tables from my applications (they also have memo files)? I don't know. Maybe because they are not opened exclusively (as are source code files)? I know from experience that vDos has issues with locking of files, at least with Lotus 123 (http://vdos.proboards.com/thread/12/lotus-fail-lock-artihmetic-errors).
Any ideas on this?
Screen and menu (as well as project and report) source files are just tables ("databases") with different extensions, I guess the error is due to corruption of the memo file (in one case, the memo file was completely missing! - I was able to recover a previous version from Dropbox history).
Why doesn't this happen with the tables from my applications (they also have memo files)? I don't know. Maybe because they are not opened exclusively (as are source code files)? I know from experience that vDos has issues with locking of files, at least with Lotus 123 (http://vdos.proboards.com/thread/12/lotus-fail-lock-artihmetic-errors).
Any ideas on this?