|
>> where the second parameter (which could never be a variable) would point to the file to use during the compile. By itself it wouldn't help. The problem lies with the sequence in which the compiler resolves file information. Right now even if you specify a literal as the file name it _still_ needs to have access to the base file. It can't use the file named in the literal. Barbara is better able to comment on this, but I know in implementing ExtFile keyword they had to compromise on this. Jon Paris Partner400 www.Partner400.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.