<Jon>
" (it's only using procedure names, not parms)" - At run time (which is what you were talking about) it is using the slot number compiled into the program at creation time. That is why it is critical when managing multiple signatures to realize that the _only_ one that really matters is *Current.
</Jon>

my statement was:
"- errors will be forced to activation time as far as the compiler could do (it's only using procedure names, not parms)"

I was talking about the compiler and this is using the names of the exports. Using export *all and doing all needed rebinds will prevent most runtime errors, wich are related to export/import.

Adding exports to the end of the binding list and faking the signature is the same as adding new fields to the end of a table record and faking the format level id with levelcheck no and avoiding some rebinds is not enough to do so.

D*B

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.