× 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.



I don't know what I was thinking when I wrote it (I'm sure I thought I was
cleaver) but I wrote a subprocedure that pulled the next invoice number.
That in itself is good, but then in the calling code, I had to do this:

dInvoice = %subst(%char(%date():*iso):1:7) + '-' +
%subst(%editc(GetNextInvoiceNumber():'X'):2:7);

WHAT THE?!? Ideally it should be:

dInvoice = GetNextInvoiceNumber();

Normally I wouldn't re-factor things like this, but now other software will
soon be creating invoices and needs to get invoice numbers. What dangers
are there in changing the subprocedure from a decimal return field to a
character? I have tracked down all of the programs that call this function
(that I know of). Or should I create a new subprocedure and leave the old
one just in case I missed something? For course if we change the format of
the number, we will quickly have problems that way.

--
Mike Wills
http://mikewills.me

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.