In a BASIC program that OPENs a file, if the file being OPENed is damaged (e.g. a bad blink or a 32-bit file that has been truncated because it tried to extend past 2 GB) the OPEN fails and the program aborts. As far as I can tell, this type of error isn't trappable and doesn't take the ON ERROR or ELSE clauses; the program simply dies an ugly death.
Anyone have any thoughts about trapping this type of error and keeping the program alive? Thanks! Jeff Fitzgerald Fitzgerald & Long, Inc. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
