05-18-2024, 11:08 AM
Ah see, the old method would simply create a size 0 file and return empty, and afterwards you couldn't even check if the file maybe not exists, as it always does exist after the OPEN call.
Well, if you take it that way, then _READFILE does exist checks, although I wouldn't take a error messagebox as a desireable exist check result nevertheless.
So my advise remains the same, always use _FILEEXIST first, if you can't guarantee the file is always there.
Well, if you take it that way, then _READFILE does exist checks, although I wouldn't take a error messagebox as a desireable exist check result nevertheless.
So my advise remains the same, always use _FILEEXIST first, if you can't guarantee the file is always there.
GuiTools, Blankers & other Projects:
https://qb64phoenix.com/forum/forumdisplay.php?fid=32
Libraries & useful Functions:
https://qb64phoenix.com/forum/forumdisplay.php?fid=23
https://qb64phoenix.com/forum/forumdisplay.php?fid=32
Libraries & useful Functions:
https://qb64phoenix.com/forum/forumdisplay.php?fid=23