|
Post by herman on Apr 29, 2021 7:18:48 GMT 1
Hello Jos,
Thanks for your explanation.
Maybe some explanation from how it comes by me, if I start the program to compile:
Booted for the first time from a fully shutdown Windows with C:\DBASE\DBASE _ALLCOM.PRG At that moment the message: file allready exist arises. (In _ALLCOM.PRG are all commands for compiling and linking (normal dBase syntaxes)) So I really don't know how not to get the notification. It comes directly after the start.
So if I close the message and give the command at the prompt then nothing is wrong. I have seen this problem since the XP era and it also does not always arise after a fresh start.
Herman
|
|
|
Post by Jos on Apr 29, 2021 8:17:40 GMT 1
I don’t know, but dBase could do something like this:
1. DIRFIRST *.TMP (finds 123.TMP) 2. DELETE 123.TMP (ok) 3. CREATE NEW FILE 123.TMP (fails)
The create command fails because 123.TMP is only marked for deletion. Although invisible, it is still there until the Windows search handle is closed by a failing DIRNEXT, a second DIRFIRST with the same DTA contents, or dBase exits. You could eventually start vDos with the log option (….vDos /log). And if the error appears, at least see in vDos.log what the offending file is.
Jos
|
|
|
Post by mrozlog on Apr 30, 2021 20:29:12 GMT 1
I am not having this issue with dBASE V (5) for DOS. I can modify my code and then compile/build/make/link with no issues.
Send me an email at ceo@dbasellc.com and I will try to help you through it. - Mike
|
|
|
Post by herman on May 1, 2021 8:35:25 GMT 1
I can also usually , but sometimes not; and I don't like dbase.com; it's not required to use that; vDos is better, in the way as I use . Herman
|
|