Files that can't open are usually solved pretty quickly either after installing the software or making the changes. The downstream elaborate errmsgs for
OPEN "CUSTOMER" TO F.CUSTOMER ELSE PRINT "CANNOT OPEN THE CUSTOMER FILE. PLEASE CONTACT YOUR PROGRAMMER. PROGRAM TERMINATING" ; STOP OPEN "INVENTORY" TO F.INVENTORY ELSE PRINT "CANNOT OPEN THE INVENTORY FILE. PLEASE CONTACT YOUR PROGRAMMER. PROGRAM TERMINATING" ; STOP or whatever the verbose message/mechanism is, is just an exercise in typing. 99.44% of the time the ELSE clause is not realized. My 1 cent. ----- Original Message ----- From: "Colin Jennings" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, September 30, 2005 9:00 AM Subject: Re: [U2] Good Programming Practice Question......... > > Sometimes, if a subroutine is only called during certain situations (thus, > > not often) and the file used by the subroutine is not used by the main > > program, opening the file within the subroutine that uses it makes sense > to > > me. > > > One problem with that Susan - what happens if the file doesn't exist or > can't be opened for some reason? I realise that this isn't exactly common, > but it was always the prime reason given to me for opening all files first > before any processing takes place. > > Col. > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
