× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 2/28/2011 9:32 PM, Scott Klement wrote:
With regard to *START/*END the restriction to use the file name is
silly. We don't have that restriction when using a key or RRN, so why do
we have it with *START/*END?

Or, if we absolutely must use a file name, then WHY OH WHY can't it give
us a clear error message that says "hey dummy, you need to use a file
name with *START/*END" instead of the really confusing and unclear RNF5319?


If I recall correctly, the reason that *START/*END aren't allowed for record formats is because of multi-format files. A key or RRN can apply to just one record format, but *START/*END applies to all formats. (I realize this is yet another case where the rules created due to the possibility of multi-format files are ruining it for all the other files.)

I agree that RNF5319 is an awful message for that error.

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.