|
Hi Jim, > We are having similar problems when a user switches from > 1 current library to another and the service programs continue to use the > files from the previous library. Yes, this is also why I don't like to keep files open... > Would it work to create only a "Close" procedure that closes all files used > in the service program and call it whenever you exit the calling program > (via LR or return). Thanks for your suggestion. I actually have coded some CloseFiles routines for usage with a series of serviceroutines I have recently created. But I'm not very happy to use this approach with lots of serviceprograms. It happened a few times to me that I forgot to define a call to a CloseFiles procedure of a serviceprogram that I used in the calling program. So that is why I consider to create a serviceprogram that registers every serviceprogram and its CloseFiles procedure when the serviceprogram is called for the first time. Best regards, Arco Simonse
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.